diff options
| author | Steven Rostedt <srostedt@redhat.com> | 2013-01-11 22:14:10 +0100 |
|---|---|---|
| committer | Steven Rostedt <rostedt@goodmis.org> | 2013-01-11 22:14:10 +0100 |
| commit | 2df8f8a6a897ebf4c5613b5be6103d33b2a21520 (patch) | |
| tree | a79d468ef6e2b41392dca68c9319f73a99a51770 /kernel/sys_ni.c | |
| parent | tracing: Fix regression of trace_options file setting (diff) | |
| download | linux-2df8f8a6a897ebf4c5613b5be6103d33b2a21520.tar.xz linux-2df8f8a6a897ebf4c5613b5be6103d33b2a21520.zip | |
tracing: Fix regression with irqsoff tracer and tracing_on file
Commit 02404baf1b47 "tracing: Remove deprecated tracing_enabled file"
removed the tracing_enabled file as it never worked properly and
the tracing_on file should be used instead. But the tracing_on file
didn't call into the tracers start/stop routines like the
tracing_enabled file did. This caused trace-cmd to break when it
enabled the irqsoff tracer.
If you just did "echo irqsoff > current_tracer" then it would work
properly. But the tool trace-cmd disables tracing first by writing
"0" into the tracing_on file. Then it writes "irqsoff" into
current_tracer and then writes "1" into tracing_on. Unfortunately,
the above commit changed the irqsoff tracer to check the tracing_on
status instead of the tracing_enabled status. If it's disabled then
it does not start the tracer internals.
The problem is that writing "1" into tracing_on does not call the
tracers "start" routine like writing "1" into tracing_enabled did.
This makes the irqsoff tracer not start when using the trace-cmd
tool, and is a regression for userspace.
Simple fix is to have the tracing_on file call the tracers start()
method when being enabled (and the stop() method when disabled).
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'kernel/sys_ni.c')
0 files changed, 0 insertions, 0 deletions