Loading kernel/trace/Kconfig +11 −6 Original line number Original line Diff line number Diff line Loading @@ -127,12 +127,17 @@ config BOOT_TRACER select TRACING select TRACING help help This tracer helps developers to optimize boot times: it records This tracer helps developers to optimize boot times: it records the timings of the initcalls. Its aim is to be parsed by the the timings of the initcalls and traces key events and the identity /scripts/bootgraph.pl tool to produce pretty graphics about of tasks that can cause boot delays, such as context-switches. boot inefficiencies, giving a visual representation of the delays during initcalls. Note that tracers self tests can't Its aim is to be parsed by the /scripts/bootgraph.pl tool to be enabled if this tracer is selected since only one tracer produce pretty graphics about boot inefficiencies, giving a visual should touch the tracing buffer at a time. representation of the delays during initcalls - but the raw /debug/tracing/trace text output is readable too. ( Note that tracing self tests can't be enabled if this tracer is selected, because the self-tests are an initcall as well and that would invalidate the boot trace. ) config STACK_TRACER config STACK_TRACER bool "Trace max stack" bool "Trace max stack" Loading Loading
kernel/trace/Kconfig +11 −6 Original line number Original line Diff line number Diff line Loading @@ -127,12 +127,17 @@ config BOOT_TRACER select TRACING select TRACING help help This tracer helps developers to optimize boot times: it records This tracer helps developers to optimize boot times: it records the timings of the initcalls. Its aim is to be parsed by the the timings of the initcalls and traces key events and the identity /scripts/bootgraph.pl tool to produce pretty graphics about of tasks that can cause boot delays, such as context-switches. boot inefficiencies, giving a visual representation of the delays during initcalls. Note that tracers self tests can't Its aim is to be parsed by the /scripts/bootgraph.pl tool to be enabled if this tracer is selected since only one tracer produce pretty graphics about boot inefficiencies, giving a visual should touch the tracing buffer at a time. representation of the delays during initcalls - but the raw /debug/tracing/trace text output is readable too. ( Note that tracing self tests can't be enabled if this tracer is selected, because the self-tests are an initcall as well and that would invalidate the boot trace. ) config STACK_TRACER config STACK_TRACER bool "Trace max stack" bool "Trace max stack" Loading