From: Fam Zheng <famz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
qemu-block@nongnu.org, Peter Lieven <pl@kamp.de>,
qemu-devel@nongnu.org, Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 8/9] block: Introduce BlockDriver.bdrv_drain callback
Date: Thu, 29 Oct 2015 09:38:39 +0800 [thread overview]
Message-ID: <20151029013839.GC19696@ad.usersys.redhat.com> (raw)
In-Reply-To: <20151028101332.GE3836@noname.str.redhat.com>
On Wed, 10/28 11:13, Kevin Wolf wrote:
> Am 26.10.2015 um 07:24 hat Fam Zheng geschrieben:
> > Drivers can have internal request sources that generate IO, like the
> > need_check_timer in QED. Since we want quiesced periods that contain
> > nested event loops in block layer, we need to have a way to disable such
> > event sources.
> >
> > Block drivers must implement the "bdrv_drain" callback if it has any
> > internal sources that can generate I/O activity, like a timer or a
> > worker thread (even in a library) that can schedule QEMUBH in an
> > asynchronous callback.
> >
> > Update the comments of bdrv_drain and bdrv_drained_begin accordingly.
> >
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > Reviewed-by: Jeff Cody <jcody@redhat.com>
> > Reviewed-by: Kevin Wolf <kwolf@redhat.com>
> > ---
> > block/io.c | 6 +++++-
> > include/block/block_int.h | 6 ++++++
> > 2 files changed, 11 insertions(+), 1 deletion(-)
> >
> > diff --git a/block/io.c b/block/io.c
> > index 358c3c4..a740827 100644
> > --- a/block/io.c
> > +++ b/block/io.c
> > @@ -234,7 +234,8 @@ bool bdrv_requests_pending(BlockDriverState *bs)
> > }
> >
> > /*
> > - * Wait for pending requests to complete on a single BlockDriverState subtree
> > + * Wait for pending requests to complete on a single BlockDriverState subtree,
> > + * and suspend block driver's internal I/O until next request arrives.
> > *
> > * Note that unlike bdrv_drain_all(), the caller must hold the BlockDriverState
> > * AioContext.
> > @@ -247,6 +248,9 @@ void bdrv_drain(BlockDriverState *bs)
> > {
> > bool busy = true;
> >
> > + if (bs->drv && bs->drv->bdrv_drain) {
> > + bs->drv->bdrv_drain(bs);
> > + }
>
> Does this need to be recursive? Recursing into bs->file and bs->backing
> would be consistent with the current bdrv_requests_pending(); but I'm
> planning to send a patch to extend this to all children.
>
Yes, I'll change it to recurse into all children.
Fam
next prev parent reply other threads:[~2015-10-29 1:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 6:24 [Qemu-devel] [PATCH 0/9] block: Fixes for bdrv_drain Fam Zheng
2015-10-26 6:24 ` [Qemu-devel] [PATCH 1/9] block: Add more types for tracked request Fam Zheng
2015-10-26 6:24 ` [Qemu-devel] [PATCH 2/9] block: Track flush requests Fam Zheng
2015-10-26 6:24 ` [Qemu-devel] [PATCH 3/9] block: Track discard requests Fam Zheng
2015-10-28 9:54 ` Kevin Wolf
2015-10-29 1:34 ` Fam Zheng
2015-10-26 6:24 ` [Qemu-devel] [PATCH 4/9] iscsi: Emulate commands in iscsi_aio_ioctl as iscsi_ioctl Fam Zheng
2015-10-28 9:51 ` Kevin Wolf
2015-10-29 1:35 ` Fam Zheng
2015-10-26 6:24 ` [Qemu-devel] [PATCH 5/9] block: Add ioctl parameter fields to BlockRequest Fam Zheng
2015-10-26 6:24 ` [Qemu-devel] [PATCH 6/9] block: Emulate bdrv_ioctl with bdrv_aio_ioctl and track both Fam Zheng
2015-10-26 6:24 ` [Qemu-devel] [PATCH 7/9] block: Drop BlockDriver.bdrv_ioctl Fam Zheng
2015-10-26 6:24 ` [Qemu-devel] [PATCH 8/9] block: Introduce BlockDriver.bdrv_drain callback Fam Zheng
2015-10-28 10:13 ` Kevin Wolf
2015-10-29 1:38 ` Fam Zheng [this message]
2015-10-26 6:24 ` [Qemu-devel] [PATCH 9/9] qed: Implement .bdrv_drain Fam Zheng
2015-10-28 10:16 ` [Qemu-devel] [PATCH 0/9] block: Fixes for bdrv_drain 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=20151029013839.GC19696@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--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).