diff options
| -rw-r--r-- | kernel/trace/Kconfig | 17 |
1 files changed, 11 insertions, 6 deletions
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig index 11fd03a429f0..1cb3e1f616af 100644 --- a/kernel/trace/Kconfig +++ b/kernel/trace/Kconfig | |||
| @@ -127,12 +127,17 @@ config BOOT_TRACER | |||
| 127 | select TRACING | 127 | select TRACING |
| 128 | help | 128 | help |
| 129 | This tracer helps developers to optimize boot times: it records | 129 | This tracer helps developers to optimize boot times: it records |
| 130 | the timings of the initcalls. Its aim is to be parsed by the | 130 | the timings of the initcalls and traces key events and the identity |
| 131 | /scripts/bootgraph.pl tool to produce pretty graphics about | 131 | of tasks that can cause boot delays, such as context-switches. |
| 132 | boot inefficiencies, giving a visual representation of the | 132 | |
| 133 | delays during initcalls. Note that tracers self tests can't | 133 | Its aim is to be parsed by the /scripts/bootgraph.pl tool to |
| 134 | be enabled if this tracer is selected since only one tracer | 134 | produce pretty graphics about boot inefficiencies, giving a visual |
| 135 | should touch the tracing buffer at a time. | 135 | representation of the delays during initcalls - but the raw |
| 136 | /debug/tracing/trace text output is readable too. | ||
| 137 | |||
| 138 | ( Note that tracing self tests can't be enabled if this tracer is | ||
| 139 | selected, because the self-tests are an initcall as well and that | ||
| 140 | would invalidate the boot trace. ) | ||
| 136 | 141 | ||
| 137 | config STACK_TRACER | 142 | config STACK_TRACER |
| 138 | bool "Trace max stack" | 143 | bool "Trace max stack" |
