Commit ad591240 authored by Steven Rostedt's avatar Steven Rostedt Committed by Ingo Molnar

ftrace: start wakeup tracing after setting function tracer

Enabling the wakeup tracer before enabling the function tracing causes
some strange results due to the dynamic enabling of the functions.
Signed-off-by: default avatarSteven Rostedt <srostedt@redhat.com>
Cc: Steven Rostedt <srostedt@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
parent b5c21b45
...@@ -352,9 +352,10 @@ static void start_wakeup_tracer(struct trace_array *tr) ...@@ -352,9 +352,10 @@ static void start_wakeup_tracer(struct trace_array *tr)
*/ */
smp_wmb(); smp_wmb();
tracer_enabled = 1;
register_ftrace_function(&trace_ops); register_ftrace_function(&trace_ops);
tracer_enabled = 1;
return; return;
fail_deprobe_wake_new: fail_deprobe_wake_new:
marker_probe_unregister("kernel_sched_wakeup_new", marker_probe_unregister("kernel_sched_wakeup_new",
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment