2 # Architectures that offer an FTRACE implementation should select HAVE_FTRACE:
7 config TRACER_MAX_TRACE
15 bool "Kernel Function Tracer"
16 depends on DEBUG_KERNEL && HAVE_FTRACE
19 select CONTEXT_SWITCH_TRACER
21 Enable the kernel to trace every kernel function. This is done
22 by using a compiler feature to insert a small, 5-byte No-Operation
23 instruction to the beginning of every kernel function, which NOP
24 sequence is then dynamically patched into a tracer call when
25 tracing is enabled by the administrator. If it's runtime disabled
26 (the bootup default), then the overhead of the instructions is very
27 small and not measurable even in micro-benchmarks.
30 bool "Scheduling Latency Tracer"
31 depends on DEBUG_KERNEL
33 select CONTEXT_SWITCH_TRACER
34 select TRACER_MAX_TRACE
36 This tracer tracks the latency of the highest priority task
37 to be scheduled in, starting from the point it has woken up.
39 config CONTEXT_SWITCH_TRACER
40 bool "Trace process context switches"
41 depends on DEBUG_KERNEL
45 This tracer gets called from the context switch and records
46 all switching of tasks.