qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: kwolf@redhat.com, stefanha@redhat.com, pbonzini@redhat.com,
	hch@lst.de, anthony@codemonkey.ws, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v2 2/7] raw_bsd: emit debug events in bdrv_co_readv() and bdrv_co_writev()
Date: Wed, 21 Aug 2013 12:41:18 +0200	[thread overview]
Message-ID: <1377081683-1600-3-git-send-email-lersek@redhat.com> (raw)
In-Reply-To: <1377081683-1600-1-git-send-email-lersek@redhat.com>

On 08/05/13 15:03, Paolo Bonzini wrote:
>
> [...]
>
> 1) BlockDriver is a struct in which these function members are
> interesting:
>
>     .bdrv_reopen_prepare
>     .bdrv_co_readv
>     .bdrv_co_writev
>     .bdrv_co_is_allocated
>     .bdrv_co_write_zeroes
>     .bdrv_co_discard
>     .bdrv_getlength
>     .bdrv_get_info
>     .bdrv_truncate
>     .bdrv_is_inserted
>     .bdrv_media_changed
>     .bdrv_eject
>     .bdrv_lock_medium
>     .bdrv_ioctl
>     .bdrv_aio_ioctl
>     .bdrv_has_zero_init
>
> They should be implemented as simple forwarders (see above). There are
> 16 functions listed here, you can easily see how this already accounts
> for 100+ SLOC roughly...
>
> The implementations of bdrv_co_readv and bdrv_co_writev should also call
> BLKDBG_EVENT on bs->file too, before forwarding to bs->file.  The events
> to be generated are BLKDBG_READ_AIO and BLKDBG_WRITE_AIO.

Signed-off-by: Laszlo Ersek <lersek@redhat.com>
---
 block/raw_bsd.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/block/raw_bsd.c b/block/raw_bsd.c
index 5c17d53..19091a3 100644
--- a/block/raw_bsd.c
+++ b/block/raw_bsd.c
@@ -33,11 +33,13 @@ static TYPE raw_reopen_prepare(BlockDriverState *bs)
 
 static TYPE raw_co_readv(BlockDriverState *bs)
 {
+    BLKDBG_EVENT(bs->file, BLKDBG_READ_AIO);
     return bdrv_co_readv(bs->file);
 }
 
 static TYPE raw_co_writev(BlockDriverState *bs)
 {
+    BLKDBG_EVENT(bs->file, BLKDBG_WRITE_AIO);
     return bdrv_co_writev(bs->file);
 }
 
-- 
1.7.1

  parent reply	other threads:[~2013-08-21 10:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21 10:41 [Qemu-devel] [PATCH v2 0/7] introduce BSD-licensed block driver for "raw" Laszlo Ersek
2013-08-21 10:41 ` [Qemu-devel] [PATCH v2 1/7] add skeleton for BSD licensed "raw" BlockDriver Laszlo Ersek
2013-08-21 10:41 ` Laszlo Ersek [this message]
2013-08-21 10:41 ` [Qemu-devel] [PATCH v2 3/7] raw_bsd: add raw_create() Laszlo Ersek
2013-08-21 10:41 ` [Qemu-devel] [PATCH v2 4/7] raw_bsd: introduce "special members" Laszlo Ersek
2013-08-21 10:41 ` [Qemu-devel] [PATCH v2 5/7] raw_bsd: add raw_create_options Laszlo Ersek
2013-08-21 10:41 ` [Qemu-devel] [PATCH v2 6/7] raw_bsd: register bdrv_raw Laszlo Ersek
2013-08-21 10:41 ` [Qemu-devel] [PATCH v2 7/7] switch raw block driver from "raw.o" to "raw_bsd.o" Laszlo Ersek
2013-08-28 10:50 ` [Qemu-devel] [PATCH v2 0/7] introduce BSD-licensed block driver for "raw" Laszlo Ersek
2013-08-28 13:17 ` Kevin Wolf

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=1377081683-1600-3-git-send-email-lersek@redhat.com \
    --to=lersek@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=hch@lst.de \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).