| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20090126180040.GA11038@ghostprotocols.net> Date: Mon, 26 Jan 2009 16:00:40 -0200 From: Arnaldo Carvalho de Melo <acme@...hat.com> To: Jens Axboe <jens.axboe@...cle.com> Cc: Ingo Molnar <mingo@...e.hu>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: blktrace: the ftrace interface needs CONFIG_TRACING 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@...cle.com> Reported-by: Ingo Molnar <mingo@...e.hu> Signed-off-by: Arnaldo Carvalho de Melo <acme@...hat.com> 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@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists