diff options
author | Steven Rostedt (Red Hat) <rostedt@goodmis.org> | 2013-03-14 12:10:40 -0400 |
---|---|---|
committer | Steven Rostedt <rostedt@goodmis.org> | 2013-03-15 00:36:08 -0400 |
commit | 328df4759c03e2c3e7429cc6cb0e180c38f32063 (patch) | |
tree | 874c0aa7642cfe8ce1e4512464eae1d33e99391b /usr/initramfs_data.S | |
parent | 4df297129f622bdc18935c856f42b9ddd18f9f28 (diff) | |
download | talos-op-linux-328df4759c03e2c3e7429cc6cb0e180c38f32063.tar.gz talos-op-linux-328df4759c03e2c3e7429cc6cb0e180c38f32063.zip |
tracing: Add function-trace option to disable function tracing of latency tracers
Currently, the only way to stop the latency tracers from doing function
tracing is to fully disable the function tracer from the proc file
system:
echo 0 > /proc/sys/kernel/ftrace_enabled
This is a big hammer approach as it disables function tracing for
all users. This includes kprobes, perf, stack tracer, etc.
Instead, create a function-trace option that the latency tracers can
check to determine if it should enable function tracing or not.
This option can be set or cleared even while the tracer is active
and the tracers will disable or enable function tracing depending
on how the option was set.
Instead of using the proc file, disable latency function tracing with
echo 0 > /debug/tracing/options/function-trace
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Clark Williams <williams@redhat.com>
Cc: John Kacur <jkacur@redhat.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'usr/initramfs_data.S')
0 files changed, 0 insertions, 0 deletions