From: Jeff Moyer <jmoyer@redhat.com>
To: jens.axboe@fusionio.com
Cc: linux-kernel@vger.kernel.org
Subject: blk_classic tracing horribly broken
Date: Thu, 22 Sep 2011 13:57:11 -0400 [thread overview]
Message-ID: <x491uv8h348.fsf@segfault.boston.devel.redhat.com> (raw)
Hi,
I've stared at the code for a while, and I've come up empty. Would
anyone care to take a stab at fixing this?
To reproduce:
mount -t debugfs none /sys/kernel/debug
cd /sys/kernel/debug/tracing
echo blk > current_tracer
echo 1 > events/block/enable
echo 1 > options/blk_classic
echo 1 > tracing_on
dd if=/dev/<device> of=/dev/null bs=1M count=1 iflag=direct
cat trace
This is what I see:
# tracer: blk
#
# DEV CPU TIMESTAMP PID ACT FLG
# | | | | | |
Unknown action 52
Unknown action 52
Unknown action bce
Unknown action 52
Unknown action 52
Unknown action 52
Unknown action 52
Unknown action 52
Unknown action 52
Unknown action 0
Unknown action 0
Unknown action 0
Unknown action 0
Unknown action 0
Unknown action 0
Unknown action 0
Unknown action 0
Unknown action 0
Unknown action 0
Unknown action 0
Unknown action 0
Unknown action 0
0,0 2 110.941937315 2584 F R [pgrep]
Unknown action 52
Unknown action 52
Unknown action 231
Unknown action 0
Unknown action 0
Unknown action 0
Unknown action 0
0,0 0 110.949383287 2584 F R [pgrep]
Unknown action 52
Unknown action 52
Unknown action 7fd1
Unknown action 0
Unknown action 0
Unknown action 0
Unknown action 0
0,0 3 110.984565328 2581 F R [ps]
Unknown action 52
Unknown action 52
Unknown action 5ad1
Unknown action 0
Unknown action 0
Unknown action 0
Unknown action 0
0,0 3 111.003843579 2581 F R [ps]
Unknown action 52
Unknown action 52
Unknown action 7551
Unknown action 0
Unknown action 0
Unknown action 0
Unknown action 0
Cheers,
Jeff
next reply other threads:[~2011-09-22 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 17:57 Jeff Moyer [this message]
2011-09-22 18:12 ` blk_classic tracing horribly broken Christoph Hellwig
2011-09-22 18:32 ` Jeff Moyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x491uv8h348.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=jens.axboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox