diff options
Diffstat (limited to 'kernel/trace/Kconfig')
-rw-r--r-- | kernel/trace/Kconfig | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig index e2a4ff6fc3a6..cc9f91e7daf4 100644 --- a/kernel/trace/Kconfig +++ b/kernel/trace/Kconfig | |||
@@ -264,6 +264,29 @@ config HW_BRANCH_TRACER | |||
264 | This tracer records all branches on the system in a circular | 264 | This tracer records all branches on the system in a circular |
265 | buffer giving access to the last N branches for each cpu. | 265 | buffer giving access to the last N branches for each cpu. |
266 | 266 | ||
267 | config KMEMTRACE | ||
268 | bool "Trace SLAB allocations" | ||
269 | select TRACING | ||
270 | select MARKERS | ||
271 | select RELAY | ||
272 | help | ||
273 | kmemtrace provides tracing for slab allocator functions, such as | ||
274 | kmalloc, kfree, kmem_cache_alloc, kmem_cache_free etc.. Collected | ||
275 | data is then fed to the userspace application in order to analyse | ||
276 | allocation hotspots, internal fragmentation and so on, making it | ||
277 | possible to see how well an allocator performs, as well as debug | ||
278 | and profile kernel code. | ||
279 | |||
280 | This requires an userspace application to use. See | ||
281 | Documentation/vm/kmemtrace.txt for more information. | ||
282 | |||
283 | Saying Y will make the kernel somewhat larger and slower. However, | ||
284 | if you disable kmemtrace at run-time or boot-time, the performance | ||
285 | impact is minimal (depending on the arch the kernel is built for). | ||
286 | |||
287 | If unsure, say N. | ||
288 | |||
289 | |||
267 | config DYNAMIC_FTRACE | 290 | config DYNAMIC_FTRACE |
268 | bool "enable/disable ftrace tracepoints dynamically" | 291 | bool "enable/disable ftrace tracepoints dynamically" |
269 | depends on FUNCTION_TRACER | 292 | depends on FUNCTION_TRACER |