[RFC PATCH 04/18] kernel/trace: add KConfig to enable blktrace_ext

[Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>]

Add kernel kconfig option for blktrace extension.

Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
---
 kernel/trace/Kconfig | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 8bd1d6d001d7..5f8c938e495f 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -456,6 +456,31 @@ config BLK_DEV_IO_TRACE
 
 	  If unsure, say N.
 
+config BLKTRACE_EXT
+	bool "Support for tracing block IO actions extensions like priority"
+	depends on BLK_DEV_IO_TRACE
+	depends on BLOCK
+	select TRACEPOINTS
+	select GENERIC_TRACER
+	select STACKTRACE
+	help
+	  Say Y here if you want to be able to trace the extended block layer
+	  actions on a given queue. Tracing allows you to see any traffic
+	  happening on a block device queue with this extension one can see
+	  the request like write-zeroes and zone reset along with the request
+	  priority. For more information (and the userspac support tools
+          needed), fetch the blktrace tools from:
+
+	  git://git.kernel.dk/blktrace.git
+
+	  Tracing also is possible using the ftrace interface, e.g.:
+
+	    echo 1 > /sys/block/sda/sda1/trace/enable
+	    echo blk > /sys/kernel/debug/tracing/current_tracer
+	    cat /sys/kernel/debug/tracing/trace_pipe
+
+	  If unsure, say N.
+
 config KPROBE_EVENTS
 	depends on KPROBES
 	depends on HAVE_REGS_AND_STACK_ACCESS_API
-- 
2.19.1