From: Jeff Moyer <jmoyer@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: jens.axboe@fusionio.com, linux-kernel@vger.kernel.org
Subject: Re: blk_classic tracing horribly broken
Date: Thu, 22 Sep 2011 14:32:29 -0400 [thread overview]
Message-ID: <x49wrd0fmwy.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20110922181216.GA13772@infradead.org> (Christoph Hellwig's message of "Thu, 22 Sep 2011 14:12:16 -0400")
Christoph Hellwig <hch@infradead.org> writes:
> On Thu, Sep 22, 2011 at 01:57:11PM -0400, Jeff Moyer wrote:
>> 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
>
> Why are you using this interface anyway? We actually had planned to
> drop it long time ago, but for some reason that never happened.
I was using it when testing the flush+fua reporting in blktrace, to be
sure we didn't break it. Since it was already broken, I didn't have to
worry, but I put it on my todo list to investigate why. Dropping broken
code is fine with me (given that there are two alternatives to use).
Cheers,
Jeff
prev parent reply other threads:[~2011-09-22 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 17:57 blk_classic tracing horribly broken Jeff Moyer
2011-09-22 18:12 ` Christoph Hellwig
2011-09-22 18:32 ` Jeff Moyer [this message]
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=x49wrd0fmwy.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=hch@infradead.org \
--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