projects / linux-2.6-block.git / blame
| Commit | Line | Data |
|---|---|---|
| 16444a8a ACM |
1 | # |
| 2 | # Architectures that offer an FTRACE implementation should select HAVE_FTRACE: | |
| 3 | # | |
| 4 | config HAVE_FTRACE | |
| 5 | bool | |
| bc0c38d1 | 6 | |
| 352ad25a SR |
7 | config TRACER_MAX_TRACE |
| 8 | bool | |
| 9 | ||
| bc0c38d1 SR |
10 | config TRACING |
| 11 | bool | |
| 12 | select DEBUG_FS | |
| 13 | ||
| 1b29b018 SR |
14 | config FTRACE |
| 15 | bool "Kernel Function Tracer" | |
| 16 | depends on DEBUG_KERNEL && HAVE_FTRACE | |
| 17 | select FRAME_POINTER | |
| 18 | select TRACING | |
| 35e8e302 | 19 | select CONTEXT_SWITCH_TRACER |
| 1b29b018 SR |
20 | help |
| 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. | |
| 35e8e302 | 28 | |
| 352ad25a SR |
29 | config SCHED_TRACER |
| 30 | bool "Scheduling Latency Tracer" | |
| 31 | depends on DEBUG_KERNEL | |
| 32 | select TRACING | |
| 33 | select CONTEXT_SWITCH_TRACER | |
| 34 | select TRACER_MAX_TRACE | |
| 35 | help | |
| 36 | This tracer tracks the latency of the highest priority task | |
| 37 | to be scheduled in, starting from the point it has woken up. | |
| 38 | ||
| 35e8e302 SR |
39 | config CONTEXT_SWITCH_TRACER |
| 40 | bool "Trace process context switches" | |
| 41 | depends on DEBUG_KERNEL | |
| 42 | select TRACING | |
| 43 | select MARKERS | |
| 44 | help | |
| 45 | This tracer gets called from the context switch and records | |
| 46 | all switching of tasks. | |
| 47 |