Skip to content

Commit 9ccba35

Browse files
committed
torture: Add more tracing crib notes to kvm.sh
This commit adds a few more hints about how to use tracing as comments at the end of kvm.sh. Signed-off-by: Paul E. McKenney <[email protected]>
1 parent 61b77be commit 9ccba35

File tree

1 file changed

+4
-0
lines changed
  • tools/testing/selftests/rcutorture/bin

1 file changed

+4
-0
lines changed

tools/testing/selftests/rcutorture/bin/kvm.sh

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -503,3 +503,7 @@ fi
503503
# Tracing: trace_event=rcu:rcu_grace_period,rcu:rcu_future_grace_period,rcu:rcu_grace_period_init,rcu:rcu_nocb_wake,rcu:rcu_preempt_task,rcu:rcu_unlock_preempted_task,rcu:rcu_quiescent_state_report,rcu:rcu_fqs,rcu:rcu_callback,rcu:rcu_kfree_callback,rcu:rcu_batch_start,rcu:rcu_invoke_callback,rcu:rcu_invoke_kfree_callback,rcu:rcu_batch_end,rcu:rcu_torture_read,rcu:rcu_barrier
504504
# Function-graph tracing: ftrace=function_graph ftrace_graph_filter=sched_setaffinity,migration_cpu_stop
505505
# Also --kconfig "CONFIG_FUNCTION_TRACER=y CONFIG_FUNCTION_GRAPH_TRACER=y"
506+
# Control buffer size: --bootargs trace_buf_size=3k
507+
# Get trace-buffer dumps on all oopses: --bootargs ftrace_dump_on_oops
508+
# Ditto, but dump only the oopsing CPU: --bootargs ftrace_dump_on_oops=orig_cpu
509+
# Heavy-handed way to also dump on warnings: --bootargs panic_on_warn

0 commit comments

Comments
 (0)