kernel_optimize_test/Documentation/trace
Steven Rostedt (Red Hat) 90e3c03c3a tracing: Add function probe to trigger a ftrace dump of current CPU trace
Add the "cpudump" command to have the current CPU ftrace buffer dumped
to console if a function is hit. This is useful when debugging a
tripple fault, where you have an idea of a function that is called
just before the tripple fault occurs, and can tell ftrace to dump its
content out to the console before it continues.

This differs from the "dump" command as it only dumps the content of
the ring buffer for the currently executing CPU, and does not show
the contents of the other CPUs.

Format is:

  <function>:cpudump

echo 'bad_address:cpudump' > /debug/tracing/set_ftrace_filter

To remove this:

echo '!bad_address:cpudump' > /debug/tracing/set_ftrace_filter

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
2013-06-11 18:38:48 -04:00
..
postprocess mm-tracepoint: rename page-free events 2012-01-10 16:30:41 -08:00
events-kmem.txt mm-tracepoint: rename page-free events 2012-01-10 16:30:41 -08:00
events-power.txt PM / tracing: remove deprecated power trace API 2013-01-26 00:39:12 +01:00
events.txt
ftrace-design.txt
ftrace.txt tracing: Add function probe to trigger a ftrace dump of current CPU trace 2013-06-11 18:38:48 -04:00
function-graph-fold.vim
kprobetrace.txt doc: fix old config name of kprobetrace 2012-09-27 12:11:29 +02:00
mmiotrace.txt
ring-buffer-design.txt
tracepoint-analysis.txt mm-tracepoint: fix documentation and examples 2012-01-10 16:30:41 -08:00
tracepoints.txt doc: Remove text on tracepoint samples 2013-03-21 10:58:03 +01:00
uprobetracer.txt uretprobes: Documentation update 2013-04-13 15:31:59 +02:00