diff options
| author | Tzvetomir Stoyanov <tstoyanov@vmware.com> | 2019-03-11 10:33:34 +0200 |
|---|---|---|
| committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2019-03-12 19:24:20 -0400 |
| commit | cd5618c3510568c47cc36629d8dd6e7fd5de56b6 (patch) | |
| tree | 5b60356fff6adc9d602f2f62243c33f73d2b31e7 | |
| parent | 2c82741856a71cc42155014b2148ab70fd63650e (diff) | |
| download | trace-cmd-cd5618c3510568c47cc36629d8dd6e7fd5de56b6.tar.gz | |
trace-cmd: Fix "trace-cmd reset" command to restore "tracing_on"
The "trace-cmd reset" command should restore ftrace to its default state.
By default, "tracing/current_tracer" is "nop" and "tracing/tracing_on" is "1".
This patch sets "tracing/tracing_on" to 1, when the command "trace-cmd reset"
is executed.
Link: http://lore.kernel.org/linux-trace-devel/20190311083339.21581-2-tstoyanov@vmware.com
Reviewed-by: Slavomir Kaslev <kaslevs@vmware.com>
Signed-off-by: Tzvetomir Stoyanov <tstoyanov@vmware.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
| -rw-r--r-- | tracecmd/trace-record.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/tracecmd/trace-record.c b/tracecmd/trace-record.c index 88b4a550..e67af106 100644 --- a/tracecmd/trace-record.c +++ b/tracecmd/trace-record.c @@ -4497,6 +4497,8 @@ void trace_reset(int argc, char **argv) clear_triggers(); tracecmd_remove_instances(); clear_func_filters(); + /* restore tracing_on to 1 */ + tracecmd_enable_tracing(); exit(0); } |