From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] dataplane: add query-blockstats support
Date: Tue, 10 Jun 2014 11:00:50 +0200 [thread overview]
Message-ID: <5396C942.3010901@redhat.com> (raw)
In-Reply-To: <1402385392-15035-1-git-send-email-stefanha@redhat.com>
Il 10/06/2014 09:29, Stefan Hajnoczi ha scritto:
> This series adds blockstats support to virtio-blk data-plane and protects
> query-blockstats from races with the dataplane IOThread.
>
> Stefan Hajnoczi (3):
> dataplane: add bdrv_acct_*() accounting
> block: make bdrv_query_stats() static
> block: acquire AioContext is qmp_query_blockstats()
>
> block/qapi.c | 6 +++++-
> hw/block/dataplane/virtio-blk.c | 10 ++++++++++
> include/block/qapi.h | 1 -
> 3 files changed, 15 insertions(+), 2 deletions(-)
>
ACK to patches 2 and 3.
Regarding patch 1 it's nice that the change is so trivial so I'm not
objecting to the patch.
However, Fam's patches for VirtIOBlockReq{,uest} unification provide
another way to achieve this. If we could drop do_rdwr_cmd in favor of
virtio_blk_handle_read and virtio_blk_handle_write, we would get for
free both blockstats and rerror/werror support. What do you think?
Paolo
next prev parent reply other threads:[~2014-06-10 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 7:29 [Qemu-devel] [PATCH 0/3] dataplane: add query-blockstats support Stefan Hajnoczi
2014-06-10 7:29 ` [Qemu-devel] [PATCH 1/3] dataplane: add bdrv_acct_*() accounting Stefan Hajnoczi
2014-06-10 7:29 ` [Qemu-devel] [PATCH 2/3] block: make bdrv_query_stats() static Stefan Hajnoczi
2014-06-10 7:29 ` [Qemu-devel] [PATCH 3/3] block: acquire AioContext is qmp_query_blockstats() Stefan Hajnoczi
2014-06-10 9:00 ` Paolo Bonzini [this message]
2014-06-18 11:10 ` [Qemu-devel] [PATCH 0/3] dataplane: add query-blockstats support Stefan Hajnoczi
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=5396C942.3010901@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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 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.