summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorSteven Rostedt <srostedt@redhat.com>2013-01-16 10:49:37 -0500
committerSteven Rostedt <rostedt@goodmis.org>2013-01-21 13:22:34 -0500
commit8741db532e86da2e54f05be751bfe1922ca63d57 (patch)
treec2687a6151b869d562e729f58651a32da5436518 /drivers
parent0f1ac8fd254b6c3e77950a1c4ee67be5dc88f7e0 (diff)
downloadblackbird-op-linux-8741db532e86da2e54f05be751bfe1922ca63d57.tar.gz
blackbird-op-linux-8741db532e86da2e54f05be751bfe1922ca63d57.zip
tracing/fgraph: Add max_graph_depth to limit function_graph depth
Add the file max_graph_depth to the debug tracing directory that lets the user define the depth of the function graph. A very useful operation is to set the depth to 1. Then it traces only the first function that is called when entering the kernel. This can be used to determine what system operations interrupt a process. For example, to work on NOHZ processes (single tasks running without a timer tick), if any interrupt goes off and preempts that task, this code will show it happening. # cd /sys/kernel/debug/tracing # echo 1 > max_graph_depth # echo function_graph > current_tracer # cat per_cpu/cpu/<cpu-of-process>/trace Cc: Frederic Weisbecker <fweisbec@gmail.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud