ftrace/fastboot: disable tracers self-tests when boot tracer is selected
The tracing engine resets the ring buffer and the tracers touch it too during self-tests. These self-tests happen during tracers registering and work against boot tracing which is logging initcalls. We have to disable tracing self-tests if the boot-tracer is selected. Reported-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
This commit is contained in:
parent
3bf77af6e1
commit
3ce2b9200d
|
@ -126,7 +126,9 @@ config BOOT_TRACER
|
||||||
the timings of the initcalls. Its aim is to be parsed by the
|
the timings of the initcalls. Its aim is to be parsed by the
|
||||||
/scripts/bootgraph.pl tool to produce pretty graphics about
|
/scripts/bootgraph.pl tool to produce pretty graphics about
|
||||||
boot inefficiencies, giving a visual representation of the
|
boot inefficiencies, giving a visual representation of the
|
||||||
delays during initcalls.
|
delays during initcalls. Note that tracers self tests can't
|
||||||
|
be enabled if this tracer is selected since only one tracer
|
||||||
|
should touch the tracing buffer at a time.
|
||||||
|
|
||||||
config STACK_TRACER
|
config STACK_TRACER
|
||||||
bool "Trace max stack"
|
bool "Trace max stack"
|
||||||
|
@ -168,8 +170,7 @@ config FTRACE_SELFTEST
|
||||||
|
|
||||||
config FTRACE_STARTUP_TEST
|
config FTRACE_STARTUP_TEST
|
||||||
bool "Perform a startup test on ftrace"
|
bool "Perform a startup test on ftrace"
|
||||||
depends on TRACING
|
depends on TRACING && DEBUG_KERNEL && !BOOT_TRACER
|
||||||
depends on DEBUG_KERNEL
|
|
||||||
select FTRACE_SELFTEST
|
select FTRACE_SELFTEST
|
||||||
help
|
help
|
||||||
This option performs a series of startup tests on ftrace. On bootup
|
This option performs a series of startup tests on ftrace. On bootup
|
||||||
|
|
Loading…
Reference in New Issue