All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: QuQ Edsel <edsel.quq@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Functions to intercept Disk IO information?
Date: Thu, 22 Oct 2015 09:22:39 +0800	[thread overview]
Message-ID: <20151022012239.GB11063@ad.usersys.redhat.com> (raw)
In-Reply-To: <CAEgxkuxfwGPya526wuP8-aqhCyswxm0nK83pvWNycsgippNz4g@mail.gmail.com>

On Thu, 10/22 01:13, QuQ Edsel wrote:
> Hi,
> My friends and I were assigned a task to find out a point to insert a
> callback function to intercept Disk IO activities such as read/write a .txt
> file. Our final goal is to generate a report for target process/file 's
> Disk IO activities. We have QEMU 2.3 with KVM enabled. We have been looking
> for such a point for long...but not so capable of such a task.
> People who had this project last year done so with TEMU 1.0 (probably QEMU
> 0.9), and the implementation point they had is dma_buf_rw(). The
> information in their report shows pid, timestamps, disk sector, buffer size
> and write/read for a target file (I am not even sure if such information is
> meaningful or useful)
> Currently I have tried to printf in functions such as dma_buf_rw /
> dma_blk_io / bdrv_aio_readv...etc. to see if they print out message when I
> open/edit/save a .txt or .jpeg file. The first one just don't print at all,
> and the second and third one print a lot after booting up the guest....
> I can see that the dma_blk_io function call in ide_dma_cb (core.c) may be
> related because it prints as I have activities on files. However it also
> prints sometime when I am not doing any thing... so I not that certain
> about it. (and I don't know if write/read activities invoke such
> function..)

Yes, dma_buf_rw should handle all your I/O unless you're doing PIO. I think the
other activities you see when you're not doing anything is from guest system's
background tasks.

Thanks,
Fam

> 
> Is there a correct /better point to intercept disk IO information
> ?(especially for activities such as read/write a .file)
> Or what should I do to clearly get the needed information from Disk IO
> functions?
> I would be so grateful to have the information.
> Thank you.
> 
> The guest environment I have is 64bit Windows 7 with qcow2 image (not sure
> if relative)
> 

  reply	other threads:[~2015-10-22  1:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 17:13 [Qemu-devel] Functions to intercept Disk IO information? QuQ Edsel
2015-10-22  1:22 ` Fam Zheng [this message]
2015-10-22  6:18   ` QuQ Edsel
2015-10-22  6:55     ` Fam Zheng

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=20151022012239.GB11063@ad.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=edsel.quq@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.