tracing: Allow tracers to start at core initcall
There's times during debugging that it is helpful to see traces of early
boot functions. But the tracers are initialized at device_initcall()
which is quite late during the boot process. Setting the kernel command
line parameter ftrace=function will not show anything until the function
tracer is initialized. This prevents being able to trace functions before
device_initcall().
There's no reason that the tracers need to be initialized so late in the
boot process. Move them up to core_initcall() as they still need to come
after early_initcall() which initializes the tracing buffers.
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by:
Steven Rostedt <rostedt@goodmis.org>
Showing
- kernel/trace/ftrace.c 2 additions, 2 deletionskernel/trace/ftrace.c
- kernel/trace/trace_branch.c 1 addition, 1 deletionkernel/trace/trace_branch.c
- kernel/trace/trace_functions.c 1 addition, 2 deletionskernel/trace/trace_functions.c
- kernel/trace/trace_functions_graph.c 1 addition, 1 deletionkernel/trace/trace_functions_graph.c
- kernel/trace/trace_irqsoff.c 1 addition, 1 deletionkernel/trace/trace_irqsoff.c
- kernel/trace/trace_sched_wakeup.c 1 addition, 1 deletionkernel/trace/trace_sched_wakeup.c
Please register or sign in to comment