[PATCH tip 1/1] blktrace: the ftrace interface needs CONFIG_TRACING
- From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
- Date: Mon, 26 Jan 2009 18:25:50 -0200
Resend, the first time I forgot to add [PATCH tip 1/1].
Ingo, this fix that problem you reported me, where a .config didn't had
CONFIG_TRACING selected.
Impact: Fix Kconfig selection for blktrace
Also mention in the help text that blktrace now can be used using
the ftrace interface.
Cc: Jens Axboe <jens.axboe@xxxxxxxxxx>
Reported-by: Ingo Molnar <mingo@xxxxxxx>
Signed-off-by: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
diff --git a/block/Kconfig b/block/Kconfig
index 0cbb3b8..7cdaa1d 100644
--- a/block/Kconfig
+++ b/block/Kconfig
@@ -50,6 +50,8 @@ config BLK_DEV_IO_TRACE
select RELAY
select DEBUG_FS
select TRACEPOINTS
+ select TRACING
+ select STACKTRACE
help
Say Y here if you want to be able to trace the block layer actions
on a given queue. Tracing allows you to see any traffic happening
@@ -58,6 +60,12 @@ config BLK_DEV_IO_TRACE
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 BLK_DEV_BSG
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH tip 1/1] blktrace: the ftrace interface needs CONFIG_TRACING
- From: Ingo Molnar
- Re: [PATCH tip 1/1] blktrace: the ftrace interface needs CONFIG_TRACING
- Prev by Date: Re: [PATCH] Fix missing ifdef in isdn_ppp
- Next by Date: Re: [PATCH] w35und: fix usb_control_msg() error handling in wb35_probe()
- Previous by thread: [ANNOUNCE]: lio-core-2.6.git updated to v2.6.29-rc2
- Next by thread: Re: [PATCH tip 1/1] blktrace: the ftrace interface needs CONFIG_TRACING
- Index(es):
Relevant Pages
|
