Linux btrace development
 help / color / mirror / Atom feed
From: Tao Ma <tm@tao.ma>
To: linux-btrace@vger.kernel.org
Subject: Re: blktrace on my block device
Date: Thu, 07 Jul 2011 09:53:05 +0000	[thread overview]
Message-ID: <4E158201.3020907@tao.ma> (raw)

On 07/07/2011 05:41 PM, Gangadhar Mylapuram wrote:
> Hi,
> 
> As for my understanding I no need to handle (BLKRESTART, BLKTRACESTOP,
> BLKTRACESETUP ..) in my device ioctl handling. It is block l/O layer
> which intercepts the
> statistics and does the job.
> 
> But for my device (not sda or hda), blktrace only show the Q events.
> It is not showing even C (completed) events. Do I need to add the
> support in my device ioctl handling code?
These trace pointers are only recorded if they are met.
So I guess the reason is that your device implements your own
make_request_fn(So you can see 'Q' event) and no other trace point is
met at all.

Thanks,
Tao

             reply	other threads:[~2011-07-07  9:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07  9:53 Tao Ma [this message]
2011-07-07  9:53 ` blktrace on my block device Gangadhar Mylapuram
2011-07-07 12:57 ` Gangadhar Mylapuram

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=4E158201.3020907@tao.ma \
    --to=tm@tao.ma \
    --cc=linux-btrace@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