tracing: Move enabling tracepoints to just after rcu_init()
authorSteven Rostedt (Red Hat) <[email protected]>
Sat, 13 Dec 2014 01:05:10 +0000 (20:05 -0500)
committerSteven Rostedt <[email protected]>
Mon, 15 Dec 2014 15:16:50 +0000 (10:16 -0500)
commit5f893b2639b21ffe6834b1aebba392c37d2b83f9
treeaff7db6baf3dd393a4791f2106ebacbe02b1ae5b
parentaee4e5f3d3abb7a2239dd02f6d8fb173413fd02f
tracing: Move enabling tracepoints to just after rcu_init()

Enabling tracepoints at boot up can be very useful. The tracepoint
can be initialized right after RCU has been. There's no need to
wait for the early_initcall() to be called. That's too late for some
things that can use tracepoints for debugging. Move the logic to
enable tracepoints out of the initcalls and into init/main.c to
right after rcu_init().

This also allows trace_printk() to be used early too.

Link: http://lkml.kernel.org/r/alpine.DEB.2.11.1412121539300.16494@nanos
Link: http://lkml.kernel.org/r/[email protected]
Reviewed-by: Paul E. McKenney <[email protected]>
Suggested-by: Thomas Gleixner <[email protected]>
Tested-by: Thomas Gleixner <[email protected]>
Acked-by: Thomas Gleixner <[email protected]>
Signed-off-by: Steven Rostedt <[email protected]>
include/linux/ftrace.h
init/main.c
kernel/trace/trace.c
kernel/trace/trace.h
kernel/trace/trace_events.c
kernel/trace/trace_syscalls.c