qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@redhat.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, avi@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] Add generic infrastructure to trace I/O
Date: Fri, 24 Oct 2008 13:55:14 -0200	[thread overview]
Message-ID: <1224863716-23793-1-git-send-email-glommer@redhat.com> (raw)

Hi guys,

Based on the discussions we had yesterday about the accel, me and anthony
had discussions that led us to think that the best way to avoid accel
hooks in the io operations is to generically keep track of I/O that 
happens throughout the execution. To demonstrate how this can be useful
besides the accelerator scope, I wrote an info iostats monitor command.

Comments welcome

             reply	other threads:[~2008-10-24 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 15:55 Glauber Costa [this message]
2008-10-24 15:55 ` [Qemu-devel] [PATCH 1/2] trace io operations Glauber Costa
2008-10-26 13:25   ` [Qemu-devel] " Avi Kivity
2008-10-24 15:55 ` [Qemu-devel] [PATCH 2/2] new monitor command: info iostats Glauber Costa
2008-10-26 13:24   ` [Qemu-devel] " Avi Kivity

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=1224863716-23793-1-git-send-email-glommer@redhat.com \
    --to=glommer@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).