mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
synced 2025-01-04 04:02:26 +00:00
Documentation: tracing: Add the startup timing of boot-time tracing
Add the note about when to start the boot-time tracing. This will be needed for the people who wants to trace earlier boot sequence. Link: https://lkml.kernel.org/r/159974156678.478751.10215894815285734481.stgit@devnote2 Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
This commit is contained in:
parent
ba0fbfbb21
commit
fd264ce96c
@ -120,6 +120,20 @@ instance node, but those are also visible from other instances. So please
|
|||||||
take care for event name conflict.
|
take care for event name conflict.
|
||||||
|
|
||||||
|
|
||||||
|
When to Start
|
||||||
|
=============
|
||||||
|
|
||||||
|
All boot-time tracing options starting with ``ftrace`` will be enabled at the
|
||||||
|
end of core_initcall. This means you can trace the events from postcore_initcall.
|
||||||
|
Most of the subsystems and architecture dependent drivers will be initialized
|
||||||
|
after that (arch_initcall or subsys_initcall). Thus, you can trace those with
|
||||||
|
boot-time tracing.
|
||||||
|
If you want to trace events before core_initcall, you can use the options
|
||||||
|
starting with ``kernel``. Some of them will be enabled eariler than the initcall
|
||||||
|
processing (for example,. ``kernel.ftrace=function`` and ``kernel.trace_event``
|
||||||
|
will start before the initcall.)
|
||||||
|
|
||||||
|
|
||||||
Examples
|
Examples
|
||||||
========
|
========
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user