From: Christoph Hellwig <hch@lst.de>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: Tracing block devices (was: Re: [Qemu-devel] Static tracepoint control via trace-event)
Date: Thu, 21 Oct 2010 07:20:27 +0200 [thread overview]
Message-ID: <20101021052027.GA15430@lst.de> (raw)
In-Reply-To: <20101019142951.GB32682@amd.home.annexia.org>
On Tue, Oct 19, 2010 at 03:29:51PM +0100, Richard W.M. Jones wrote:
> On Tue, Oct 19, 2010 at 03:59:36PM +0200, Jan Kiszka wrote:
> > Once we have "-trace events=...", defining the list of active
> > tracepoints before starting qemu will be trivial (e.g. via a config
> > file). Of course, this requires that all tracepoints are built-in...
>
> Sorry that I've not been following this very closely, but does this
> sort of thing allow tracing reads and writes to block devices? Am I
> right in thinking that if a tracepoint existed in the right place, one
> could get a log file from that which could be post-processed in
> another tool?
I don't think it does. But I have a patch that I need to update which
outputs traces in the form of the Linux blktrace block I/O tracing tool,
which does exactly what you need (and more). You can simply use
all the blktrace-enabled tools, including seekwatcher on it.
next prev parent reply other threads:[~2010-10-21 5:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 13:08 [Qemu-devel] Static tracepoint control via trace-event Jan Kiszka
2010-10-19 13:30 ` [Qemu-devel] " Stefan Hajnoczi
2010-10-19 13:46 ` Jan Kiszka
2010-10-19 14:03 ` Stefan Hajnoczi
2010-10-19 14:12 ` Daniel P. Berrange
2010-10-19 14:30 ` Jan Kiszka
2010-10-19 13:36 ` [Qemu-devel] " Daniel P. Berrange
2010-10-19 13:52 ` Stefan Hajnoczi
2010-10-19 13:59 ` Jan Kiszka
2010-10-19 14:29 ` Tracing block devices (was: Re: [Qemu-devel] Static tracepoint control via trace-event) Richard W.M. Jones
2010-10-19 14:38 ` [Qemu-devel] Re: Tracing block devices Jan Kiszka
2010-10-19 14:44 ` Tracing block devices (was: Re: [Qemu-devel] Static tracepoint control via trace-event) Stefan Hajnoczi
2010-10-21 5:20 ` Christoph Hellwig [this message]
2010-10-21 7:38 ` Richard W.M. Jones
2010-10-21 9:04 ` Stefan Hajnoczi
2010-10-21 8:51 ` Daniel P. Berrange
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=20101021052027.GA15430@lst.de \
--to=hch@lst.de \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).