| Kconfig (d95c3578120e5bc4784069439f00ccb1b5f87717) | Kconfig (ee08c6eccb7d1295516f7cf420fddf7b14e9146f) |
|---|---|
| 1# 2# Architectures that offer an FUNCTION_TRACER implementation should 3# select HAVE_FUNCTION_TRACER: 4# 5 6config USER_STACKTRACE_SUPPORT 7 bool 8 9config NOP_TRACER 10 bool 11 | 1# 2# Architectures that offer an FUNCTION_TRACER implementation should 3# select HAVE_FUNCTION_TRACER: 4# 5 6config USER_STACKTRACE_SUPPORT 7 bool 8 9config NOP_TRACER 10 bool 11 |
| 12config HAVE_FTRACE_NMI_ENTER 13 bool 14 |
|
| 12config HAVE_FUNCTION_TRACER 13 bool 14 15config HAVE_FUNCTION_GRAPH_TRACER 16 bool 17 18config HAVE_FUNCTION_TRACE_MCOUNT_TEST 19 bool --- 6 unchanged lines hidden (view full) --- 26 bool 27 28config HAVE_FTRACE_MCOUNT_RECORD 29 bool 30 31config HAVE_HW_BRANCH_TRACER 32 bool 33 | 15config HAVE_FUNCTION_TRACER 16 bool 17 18config HAVE_FUNCTION_GRAPH_TRACER 19 bool 20 21config HAVE_FUNCTION_TRACE_MCOUNT_TEST 22 bool --- 6 unchanged lines hidden (view full) --- 29 bool 30 31config HAVE_FTRACE_MCOUNT_RECORD 32 bool 33 34config HAVE_HW_BRANCH_TRACER 35 bool 36 |
| 37config HAVE_FTRACE_SYSCALLS 38 bool 39 |
|
| 34config TRACER_MAX_TRACE 35 bool 36 37config RING_BUFFER 38 bool 39 | 40config TRACER_MAX_TRACE 41 bool 42 43config RING_BUFFER 44 bool 45 |
| 46config FTRACE_NMI_ENTER 47 bool 48 depends on HAVE_FTRACE_NMI_ENTER 49 default y 50 |
|
| 40config TRACING 41 bool 42 select DEBUG_FS 43 select RING_BUFFER 44 select STACKTRACE if STACKTRACE_SUPPORT 45 select TRACEPOINTS 46 select NOP_TRACER | 51config TRACING 52 bool 53 select DEBUG_FS 54 select RING_BUFFER 55 select STACKTRACE if STACKTRACE_SUPPORT 56 select TRACEPOINTS 57 select NOP_TRACER |
| 58 select BINARY_PRINTF |
|
| 47 | 59 |
| 60# 61# Minimum requirements an architecture has to meet for us to 62# be able to offer generic tracing facilities: 63# 64config TRACING_SUPPORT 65 bool 66 depends on TRACE_IRQFLAGS_SUPPORT 67 depends on STACKTRACE_SUPPORT 68 default y 69 70if TRACING_SUPPORT 71 |
|
| 48menu "Tracers" 49 50config FUNCTION_TRACER 51 bool "Kernel Function Tracer" 52 depends on HAVE_FUNCTION_TRACER | 72menu "Tracers" 73 74config FUNCTION_TRACER 75 bool "Kernel Function Tracer" 76 depends on HAVE_FUNCTION_TRACER |
| 53 depends on DEBUG_KERNEL | |
| 54 select FRAME_POINTER 55 select KALLSYMS 56 select TRACING 57 select CONTEXT_SWITCH_TRACER 58 help 59 Enable the kernel to trace every kernel function. This is done 60 by using a compiler feature to insert a small, 5-byte No-Operation 61 instruction to the beginning of every kernel function, which NOP --- 16 unchanged lines hidden (view full) --- 78 This is done by setting the current return address on the current 79 task structure into a stack of calls. 80 81config IRQSOFF_TRACER 82 bool "Interrupts-off Latency Tracer" 83 default n 84 depends on TRACE_IRQFLAGS_SUPPORT 85 depends on GENERIC_TIME | 77 select FRAME_POINTER 78 select KALLSYMS 79 select TRACING 80 select CONTEXT_SWITCH_TRACER 81 help 82 Enable the kernel to trace every kernel function. This is done 83 by using a compiler feature to insert a small, 5-byte No-Operation 84 instruction to the beginning of every kernel function, which NOP --- 16 unchanged lines hidden (view full) --- 101 This is done by setting the current return address on the current 102 task structure into a stack of calls. 103 104config IRQSOFF_TRACER 105 bool "Interrupts-off Latency Tracer" 106 default n 107 depends on TRACE_IRQFLAGS_SUPPORT 108 depends on GENERIC_TIME |
| 86 depends on DEBUG_KERNEL | |
| 87 select TRACE_IRQFLAGS 88 select TRACING 89 select TRACER_MAX_TRACE 90 help 91 This option measures the time spent in irqs-off critical 92 sections, with microsecond accuracy. 93 94 The default measurement method is a maximum search, which is --- 6 unchanged lines hidden (view full) --- 101 enabled. This option and the preempt-off timing option can be 102 used together or separately.) 103 104config PREEMPT_TRACER 105 bool "Preemption-off Latency Tracer" 106 default n 107 depends on GENERIC_TIME 108 depends on PREEMPT | 109 select TRACE_IRQFLAGS 110 select TRACING 111 select TRACER_MAX_TRACE 112 help 113 This option measures the time spent in irqs-off critical 114 sections, with microsecond accuracy. 115 116 The default measurement method is a maximum search, which is --- 6 unchanged lines hidden (view full) --- 123 enabled. This option and the preempt-off timing option can be 124 used together or separately.) 125 126config PREEMPT_TRACER 127 bool "Preemption-off Latency Tracer" 128 default n 129 depends on GENERIC_TIME 130 depends on PREEMPT |
| 109 depends on DEBUG_KERNEL | |
| 110 select TRACING 111 select TRACER_MAX_TRACE 112 help 113 This option measures the time spent in preemption off critical 114 sections, with microsecond accuracy. 115 116 The default measurement method is a maximum search, which is 117 disabled by default and can be runtime (re-)started --- 4 unchanged lines hidden (view full) --- 122 (Note that kernel size and overhead increases with this option 123 enabled. This option and the irqs-off timing option can be 124 used together or separately.) 125 126config SYSPROF_TRACER 127 bool "Sysprof Tracer" 128 depends on X86 129 select TRACING | 131 select TRACING 132 select TRACER_MAX_TRACE 133 help 134 This option measures the time spent in preemption off critical 135 sections, with microsecond accuracy. 136 137 The default measurement method is a maximum search, which is 138 disabled by default and can be runtime (re-)started --- 4 unchanged lines hidden (view full) --- 143 (Note that kernel size and overhead increases with this option 144 enabled. This option and the irqs-off timing option can be 145 used together or separately.) 146 147config SYSPROF_TRACER 148 bool "Sysprof Tracer" 149 depends on X86 150 select TRACING |
| 151 select CONTEXT_SWITCH_TRACER |
|
| 130 help 131 This tracer provides the trace needed by the 'Sysprof' userspace 132 tool. 133 134config SCHED_TRACER 135 bool "Scheduling Latency Tracer" | 152 help 153 This tracer provides the trace needed by the 'Sysprof' userspace 154 tool. 155 156config SCHED_TRACER 157 bool "Scheduling Latency Tracer" |
| 136 depends on DEBUG_KERNEL | |
| 137 select TRACING 138 select CONTEXT_SWITCH_TRACER 139 select TRACER_MAX_TRACE 140 help 141 This tracer tracks the latency of the highest priority task 142 to be scheduled in, starting from the point it has woken up. 143 144config CONTEXT_SWITCH_TRACER 145 bool "Trace process context switches" | 158 select TRACING 159 select CONTEXT_SWITCH_TRACER 160 select TRACER_MAX_TRACE 161 help 162 This tracer tracks the latency of the highest priority task 163 to be scheduled in, starting from the point it has woken up. 164 165config CONTEXT_SWITCH_TRACER 166 bool "Trace process context switches" |
| 146 depends on DEBUG_KERNEL | |
| 147 select TRACING 148 select MARKERS 149 help 150 This tracer gets called from the context switch and records 151 all switching of tasks. 152 | 167 select TRACING 168 select MARKERS 169 help 170 This tracer gets called from the context switch and records 171 all switching of tasks. 172 |
| 173config EVENT_TRACER 174 bool "Trace various events in the kernel" 175 select TRACING 176 help 177 This tracer hooks to various trace points in the kernel 178 allowing the user to pick and choose which trace point they 179 want to trace. 180 181config FTRACE_SYSCALLS 182 bool "Trace syscalls" 183 depends on HAVE_FTRACE_SYSCALLS 184 select TRACING 185 help 186 Basic tracer to catch the syscall entry and exit events. 187 |
|
| 153config BOOT_TRACER 154 bool "Trace boot initcalls" | 188config BOOT_TRACER 189 bool "Trace boot initcalls" |
| 155 depends on DEBUG_KERNEL | |
| 156 select TRACING 157 select CONTEXT_SWITCH_TRACER 158 help 159 This tracer helps developers to optimize boot times: it records 160 the timings of the initcalls and traces key events and the identity 161 of tasks that can cause boot delays, such as context-switches. 162 163 Its aim is to be parsed by the /scripts/bootgraph.pl tool to 164 produce pretty graphics about boot inefficiencies, giving a visual 165 representation of the delays during initcalls - but the raw 166 /debug/tracing/trace text output is readable too. 167 | 190 select TRACING 191 select CONTEXT_SWITCH_TRACER 192 help 193 This tracer helps developers to optimize boot times: it records 194 the timings of the initcalls and traces key events and the identity 195 of tasks that can cause boot delays, such as context-switches. 196 197 Its aim is to be parsed by the /scripts/bootgraph.pl tool to 198 produce pretty graphics about boot inefficiencies, giving a visual 199 representation of the delays during initcalls - but the raw 200 /debug/tracing/trace text output is readable too. 201 |
| 168 ( Note that tracing self tests can't be enabled if this tracer is 169 selected, because the self-tests are an initcall as well and that 170 would invalidate the boot trace. ) | 202 You must pass in ftrace=initcall to the kernel command line 203 to enable this on bootup. |
| 171 172config TRACE_BRANCH_PROFILING 173 bool "Trace likely/unlikely profiler" | 204 205config TRACE_BRANCH_PROFILING 206 bool "Trace likely/unlikely profiler" |
| 174 depends on DEBUG_KERNEL | |
| 175 select TRACING 176 help 177 This tracer profiles all the the likely and unlikely macros 178 in the kernel. It will display the results in: 179 180 /debugfs/tracing/profile_annotated_branch 181 182 Note: this will add a significant overhead, only turn this --- 36 unchanged lines hidden (view full) --- 219 histogram of the callers, but actually places the calling 220 events into a running trace buffer to see when and where the 221 events happened, as well as their results. 222 223 Say N if unsure. 224 225config POWER_TRACER 226 bool "Trace power consumption behavior" | 207 select TRACING 208 help 209 This tracer profiles all the the likely and unlikely macros 210 in the kernel. It will display the results in: 211 212 /debugfs/tracing/profile_annotated_branch 213 214 Note: this will add a significant overhead, only turn this --- 36 unchanged lines hidden (view full) --- 251 histogram of the callers, but actually places the calling 252 events into a running trace buffer to see when and where the 253 events happened, as well as their results. 254 255 Say N if unsure. 256 257config POWER_TRACER 258 bool "Trace power consumption behavior" |
| 227 depends on DEBUG_KERNEL | |
| 228 depends on X86 229 select TRACING 230 help 231 This tracer helps developers to analyze and optimize the kernels 232 power management decisions, specifically the C-state and P-state 233 behavior. 234 235 236config STACK_TRACER 237 bool "Trace max stack" 238 depends on HAVE_FUNCTION_TRACER | 259 depends on X86 260 select TRACING 261 help 262 This tracer helps developers to analyze and optimize the kernels 263 power management decisions, specifically the C-state and P-state 264 behavior. 265 266 267config STACK_TRACER 268 bool "Trace max stack" 269 depends on HAVE_FUNCTION_TRACER |
| 239 depends on DEBUG_KERNEL | |
| 240 select FUNCTION_TRACER 241 select STACKTRACE 242 select KALLSYMS 243 help 244 This special tracer records the maximum stack footprint of the 245 kernel and displays it in debugfs/tracing/stack_trace. 246 247 This tracer works by hooking into every function call that the --- 13 unchanged lines hidden (view full) --- 261config HW_BRANCH_TRACER 262 depends on HAVE_HW_BRANCH_TRACER 263 bool "Trace hw branches" 264 select TRACING 265 help 266 This tracer records all branches on the system in a circular 267 buffer giving access to the last N branches for each cpu. 268 | 270 select FUNCTION_TRACER 271 select STACKTRACE 272 select KALLSYMS 273 help 274 This special tracer records the maximum stack footprint of the 275 kernel and displays it in debugfs/tracing/stack_trace. 276 277 This tracer works by hooking into every function call that the --- 13 unchanged lines hidden (view full) --- 291config HW_BRANCH_TRACER 292 depends on HAVE_HW_BRANCH_TRACER 293 bool "Trace hw branches" 294 select TRACING 295 help 296 This tracer records all branches on the system in a circular 297 buffer giving access to the last N branches for each cpu. 298 |
| 299config KMEMTRACE 300 bool "Trace SLAB allocations" 301 select TRACING 302 help 303 kmemtrace provides tracing for slab allocator functions, such as 304 kmalloc, kfree, kmem_cache_alloc, kmem_cache_free etc.. Collected 305 data is then fed to the userspace application in order to analyse 306 allocation hotspots, internal fragmentation and so on, making it 307 possible to see how well an allocator performs, as well as debug 308 and profile kernel code. 309 310 This requires an userspace application to use. See 311 Documentation/vm/kmemtrace.txt for more information. 312 313 Saying Y will make the kernel somewhat larger and slower. However, 314 if you disable kmemtrace at run-time or boot-time, the performance 315 impact is minimal (depending on the arch the kernel is built for). 316 317 If unsure, say N. 318 319config WORKQUEUE_TRACER 320 bool "Trace workqueues" 321 select TRACING 322 help 323 The workqueue tracer provides some statistical informations 324 about each cpu workqueue thread such as the number of the 325 works inserted and executed since their creation. It can help 326 to evaluate the amount of work each of them have to perform. 327 For example it can help a developer to decide whether he should 328 choose a per cpu workqueue instead of a singlethreaded one. 329 330config BLK_DEV_IO_TRACE 331 bool "Support for tracing block io actions" 332 depends on SYSFS 333 depends on BLOCK 334 select RELAY 335 select DEBUG_FS 336 select TRACEPOINTS 337 select TRACING 338 select STACKTRACE 339 help 340 Say Y here if you want to be able to trace the block layer actions 341 on a given queue. Tracing allows you to see any traffic happening 342 on a block device queue. For more information (and the userspace 343 support tools needed), fetch the blktrace tools from: 344 345 git://git.kernel.dk/blktrace.git 346 347 Tracing also is possible using the ftrace interface, e.g.: 348 349 echo 1 > /sys/block/sda/sda1/trace/enable 350 echo blk > /sys/kernel/debug/tracing/current_tracer 351 cat /sys/kernel/debug/tracing/trace_pipe 352 353 If unsure, say N. 354 |
|
| 269config DYNAMIC_FTRACE 270 bool "enable/disable ftrace tracepoints dynamically" 271 depends on FUNCTION_TRACER 272 depends on HAVE_DYNAMIC_FTRACE | 355config DYNAMIC_FTRACE 356 bool "enable/disable ftrace tracepoints dynamically" 357 depends on FUNCTION_TRACER 358 depends on HAVE_DYNAMIC_FTRACE |
| 273 depends on DEBUG_KERNEL | |
| 274 default y 275 help 276 This option will modify all the calls to ftrace dynamically 277 (will patch them out of the binary image and replaces them 278 with a No-Op instruction) as they are called. A table is 279 created to dynamically enable them again. 280 281 This way a CONFIG_FUNCTION_TRACER kernel is slightly larger, but otherwise --- 9 unchanged lines hidden (view full) --- 291 depends on DYNAMIC_FTRACE 292 depends on HAVE_FTRACE_MCOUNT_RECORD 293 294config FTRACE_SELFTEST 295 bool 296 297config FTRACE_STARTUP_TEST 298 bool "Perform a startup test on ftrace" | 359 default y 360 help 361 This option will modify all the calls to ftrace dynamically 362 (will patch them out of the binary image and replaces them 363 with a No-Op instruction) as they are called. A table is 364 created to dynamically enable them again. 365 366 This way a CONFIG_FUNCTION_TRACER kernel is slightly larger, but otherwise --- 9 unchanged lines hidden (view full) --- 376 depends on DYNAMIC_FTRACE 377 depends on HAVE_FTRACE_MCOUNT_RECORD 378 379config FTRACE_SELFTEST 380 bool 381 382config FTRACE_STARTUP_TEST 383 bool "Perform a startup test on ftrace" |
| 299 depends on TRACING && DEBUG_KERNEL && !BOOT_TRACER | 384 depends on TRACING |
| 300 select FTRACE_SELFTEST 301 help 302 This option performs a series of startup tests on ftrace. On bootup 303 a series of tests are made to verify that the tracer is 304 functioning properly. It will do tests on all the configured 305 tracers of ftrace. 306 307config MMIOTRACE 308 bool "Memory mapped IO tracing" | 385 select FTRACE_SELFTEST 386 help 387 This option performs a series of startup tests on ftrace. On bootup 388 a series of tests are made to verify that the tracer is 389 functioning properly. It will do tests on all the configured 390 tracers of ftrace. 391 392config MMIOTRACE 393 bool "Memory mapped IO tracing" |
| 309 depends on HAVE_MMIOTRACE_SUPPORT && DEBUG_KERNEL && PCI | 394 depends on HAVE_MMIOTRACE_SUPPORT && PCI |
| 310 select TRACING 311 help 312 Mmiotrace traces Memory Mapped I/O access and is meant for 313 debugging and reverse engineering. It is called from the ioremap 314 implementation and works via page faults. Tracing is disabled by 315 default and can be enabled at run-time. 316 317 See Documentation/tracers/mmiotrace.txt. --- 5 unchanged lines hidden (view full) --- 323 help 324 This is a dumb module for testing mmiotrace. It is very dangerous 325 as it will write garbage to IO memory starting at a given address. 326 However, it should be safe to use on e.g. unused portion of VRAM. 327 328 Say N, unless you absolutely know what you are doing. 329 330endmenu | 395 select TRACING 396 help 397 Mmiotrace traces Memory Mapped I/O access and is meant for 398 debugging and reverse engineering. It is called from the ioremap 399 implementation and works via page faults. Tracing is disabled by 400 default and can be enabled at run-time. 401 402 See Documentation/tracers/mmiotrace.txt. --- 5 unchanged lines hidden (view full) --- 408 help 409 This is a dumb module for testing mmiotrace. It is very dangerous 410 as it will write garbage to IO memory starting at a given address. 411 However, it should be safe to use on e.g. unused portion of VRAM. 412 413 Say N, unless you absolutely know what you are doing. 414 415endmenu |
| 416 417endif # TRACING_SUPPORT 418 |
|