diff options
| author | Steven Rostedt <srostedt@redhat.com> | 2012-10-05 12:13:07 -0400 |
|---|---|---|
| committer | Steven Rostedt <rostedt@goodmis.org> | 2012-10-31 16:45:24 -0400 |
| commit | 6f4156723c084bfc0c0f72205c541fafb8ad3ded (patch) | |
| tree | 1852fb096d1f45a6d826480b41f9d7eb292c4e8a /kernel/trace/trace_branch.c | |
| parent | bcd83ea6cbfee54e33d1527b87538dc99ca2137b (diff) | |
| download | op-kernel-dev-6f4156723c084bfc0c0f72205c541fafb8ad3ded.zip op-kernel-dev-6f4156723c084bfc0c0f72205c541fafb8ad3ded.tar.gz | |
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>
Diffstat (limited to 'kernel/trace/trace_branch.c')
| -rw-r--r-- | kernel/trace/trace_branch.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/trace/trace_branch.c b/kernel/trace/trace_branch.c index 8d3538b..bd3e0ee 100644 --- a/kernel/trace/trace_branch.c +++ b/kernel/trace/trace_branch.c @@ -199,7 +199,7 @@ __init static int init_branch_tracer(void) } return register_tracer(&branch_trace); } -device_initcall(init_branch_tracer); +core_initcall(init_branch_tracer); #else static inline |
