| Kconfig (b2576e1d4408e134e2188c967b1f28af39cd79d4) | Kconfig (fe6f90e57fd31af8daca534ea01db2e5666c15da) |
|---|---|
| 1# 2# Architectures that offer an FUNCTION_TRACER implementation should 3# select HAVE_FUNCTION_TRACER: 4# 5 6config USER_STACKTRACE_SUPPORT 7 bool 8 --- 250 unchanged lines hidden (view full) --- 259config HW_BRANCH_TRACER 260 depends on HAVE_HW_BRANCH_TRACER 261 bool "Trace hw branches" 262 select TRACING 263 help 264 This tracer records all branches on the system in a circular 265 buffer giving access to the last N branches for each cpu. 266 | 1# 2# Architectures that offer an FUNCTION_TRACER implementation should 3# select HAVE_FUNCTION_TRACER: 4# 5 6config USER_STACKTRACE_SUPPORT 7 bool 8 --- 250 unchanged lines hidden (view full) --- 259config HW_BRANCH_TRACER 260 depends on HAVE_HW_BRANCH_TRACER 261 bool "Trace hw branches" 262 select TRACING 263 help 264 This tracer records all branches on the system in a circular 265 buffer giving access to the last N branches for each cpu. 266 |
| 267config KMEMTRACE 268 bool "Trace SLAB allocations" 269 select TRACING 270 help 271 kmemtrace provides tracing for slab allocator functions, such as 272 kmalloc, kfree, kmem_cache_alloc, kmem_cache_free etc.. Collected 273 data is then fed to the userspace application in order to analyse 274 allocation hotspots, internal fragmentation and so on, making it 275 possible to see how well an allocator performs, as well as debug 276 and profile kernel code. 277 278 This requires an userspace application to use. See 279 Documentation/vm/kmemtrace.txt for more information. 280 281 Saying Y will make the kernel somewhat larger and slower. However, 282 if you disable kmemtrace at run-time or boot-time, the performance 283 impact is minimal (depending on the arch the kernel is built for). 284 285 If unsure, say N. 286 287 |
|
| 267config DYNAMIC_FTRACE 268 bool "enable/disable ftrace tracepoints dynamically" 269 depends on FUNCTION_TRACER 270 depends on HAVE_DYNAMIC_FTRACE 271 depends on DEBUG_KERNEL 272 default y 273 help 274 This option will modify all the calls to ftrace dynamically --- 22 unchanged lines hidden (view full) --- 297 depends on TRACING && DEBUG_KERNEL && !BOOT_TRACER 298 select FTRACE_SELFTEST 299 help 300 This option performs a series of startup tests on ftrace. On bootup 301 a series of tests are made to verify that the tracer is 302 functioning properly. It will do tests on all the configured 303 tracers of ftrace. 304 | 288config DYNAMIC_FTRACE 289 bool "enable/disable ftrace tracepoints dynamically" 290 depends on FUNCTION_TRACER 291 depends on HAVE_DYNAMIC_FTRACE 292 depends on DEBUG_KERNEL 293 default y 294 help 295 This option will modify all the calls to ftrace dynamically --- 22 unchanged lines hidden (view full) --- 318 depends on TRACING && DEBUG_KERNEL && !BOOT_TRACER 319 select FTRACE_SELFTEST 320 help 321 This option performs a series of startup tests on ftrace. On bootup 322 a series of tests are made to verify that the tracer is 323 functioning properly. It will do tests on all the configured 324 tracers of ftrace. 325 |
| 326config MMIOTRACE 327 bool "Memory mapped IO tracing" 328 depends on HAVE_MMIOTRACE_SUPPORT && DEBUG_KERNEL && PCI 329 select TRACING 330 help 331 Mmiotrace traces Memory Mapped I/O access and is meant for 332 debugging and reverse engineering. It is called from the ioremap 333 implementation and works via page faults. Tracing is disabled by 334 default and can be enabled at run-time. 335 336 See Documentation/tracers/mmiotrace.txt. 337 If you are not helping to develop drivers, say N. 338 339config MMIOTRACE_TEST 340 tristate "Test module for mmiotrace" 341 depends on MMIOTRACE && m 342 help 343 This is a dumb module for testing mmiotrace. It is very dangerous 344 as it will write garbage to IO memory starting at a given address. 345 However, it should be safe to use on e.g. unused portion of VRAM. 346 347 Say N, unless you absolutely know what you are doing. 348 |
|
| 305endmenu | 349endmenu |