aboutsummaryrefslogtreecommitdiffstats
path: root/kernel/trace/Kconfig
diff options
context:
space:
mode:
Diffstat (limited to 'kernel/trace/Kconfig')
-rw-r--r--kernel/trace/Kconfig23
1 files changed, 23 insertions, 0 deletions
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 25131a5d5e4f..4fee43c01942 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -302,6 +302,29 @@ config WORKQUEUE_TRACER
302 For example it can help a developer to decide whether he should 302 For example it can help a developer to decide whether he should
303 choose a per cpu workqueue instead of a singlethreaded one. 303 choose a per cpu workqueue instead of a singlethreaded one.
304 304
305config BLK_DEV_IO_TRACE
306 bool "Support for tracing block io actions"
307 depends on SYSFS
308 select RELAY
309 select DEBUG_FS
310 select TRACEPOINTS
311 select TRACING
312 select STACKTRACE
313 help
314 Say Y here if you want to be able to trace the block layer actions
315 on a given queue. Tracing allows you to see any traffic happening
316 on a block device queue. For more information (and the userspace
317 support tools needed), fetch the blktrace tools from:
318
319 git://git.kernel.dk/blktrace.git
320
321 Tracing also is possible using the ftrace interface, e.g.:
322
323 echo 1 > /sys/block/sda/sda1/trace/enable
324 echo blk > /sys/kernel/debug/tracing/current_tracer
325 cat /sys/kernel/debug/tracing/trace_pipe
326
327 If unsure, say N.
305 328
306config DYNAMIC_FTRACE 329config DYNAMIC_FTRACE
307 bool "enable/disable ftrace tracepoints dynamically" 330 bool "enable/disable ftrace tracepoints dynamically"