From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
qemu-block@nongnu.org, Ed Swierk <eswierk@skyportsystems.com>,
Max Reitz <mreitz@redhat.com>, Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 4/6] block: Quiesce old aio context during bdrv_set_aio_context
Date: Mon, 10 Apr 2017 11:11:17 +0200 [thread overview]
Message-ID: <20170410091117.GD4883@noname.redhat.com> (raw)
In-Reply-To: <20170410084551.GD14050@lemon>
Am 10.04.2017 um 10:45 hat Fam Zheng geschrieben:
> On Mon, 04/10 10:06, Kevin Wolf wrote:
> > Am 08.04.2017 um 05:43 hat Fam Zheng geschrieben:
> > > On Fri, 04/07 13:50, Stefan Hajnoczi wrote:
> > > > On Fri, Apr 07, 2017 at 02:54:12PM +0800, Fam Zheng wrote:
> > > > > @@ -4413,6 +4416,10 @@ void bdrv_set_aio_context(BlockDriverState *bs, AioContext *new_context)
> > > > > aio_context_acquire(new_context);
> > > > > bdrv_attach_aio_context(bs, new_context);
> > > > > aio_context_release(new_context);
> > > > > + if (bs->job) {
> > > > > + block_job_resume(bs->job);
> > > > > + }
> > > >
> > > > Should this be called before aio_context_release(new_context)?
> > >
> > > Yes, and I'm going to replace it with bdrv_parent_drained_begin() as Kevin
> > > suggested.
> >
> > I think at the moment bdrv_parent_drained_begin() can't replace it yet,
> > but you need both.
>
> I think we have it already, see 600ac6a0e (blockjob: add devops to blockjob
> backends):
>
> bdrv_parent_drained_begin
> -> blk_root_drained_begin
> -> block_job_drained_begin
> -> block_job_pause
Ah, yes, you're right. Somehow I thought this was only for 2.10.
Kevin
next prev parent reply other threads:[~2017-04-10 9:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 6:54 [Qemu-devel] [PATCH v2 0/6] block: Fixes regarding dataplane and management operations Fam Zheng
2017-04-07 6:54 ` [Qemu-devel] [PATCH v2 1/6] block: Fix unpaired aio_disable_external in external snapshot Fam Zheng
2017-04-07 13:23 ` Stefan Hajnoczi
2017-04-07 6:54 ` [Qemu-devel] [PATCH v2 2/6] block: Assert attached child node has right aio context Fam Zheng
2017-04-07 13:24 ` Stefan Hajnoczi
2017-04-07 6:54 ` [Qemu-devel] [PATCH v2 3/6] mirror: Fix aio context of mirror_top_bs Fam Zheng
2017-04-07 13:24 ` Stefan Hajnoczi
2017-04-07 6:54 ` [Qemu-devel] [PATCH v2 4/6] block: Quiesce old aio context during bdrv_set_aio_context Fam Zheng
2017-04-07 12:50 ` Stefan Hajnoczi
2017-04-08 3:43 ` Fam Zheng
2017-04-10 8:06 ` Kevin Wolf
2017-04-10 8:45 ` Fam Zheng
2017-04-10 9:11 ` Kevin Wolf [this message]
2017-04-07 6:54 ` [Qemu-devel] [PATCH v2 5/6] coroutine: Explicitly specify AioContext when entering coroutine Fam Zheng
2017-04-07 9:57 ` Fam Zheng
2017-04-07 13:26 ` Stefan Hajnoczi
2017-04-08 3:27 ` Fam Zheng
2017-04-07 14:07 ` Eric Blake
2017-04-07 15:14 ` Kevin Wolf
2017-04-10 0:56 ` Paolo Bonzini
2017-04-10 1:43 ` Fam Zheng
2017-04-07 6:54 ` [Qemu-devel] [PATCH v2 6/6] tests/block-job-txn: Don't start block job before adding to txn Fam Zheng
2017-04-07 13:28 ` Stefan Hajnoczi
2017-04-07 18:05 ` John Snow
2017-04-08 3:39 ` Fam Zheng
2017-04-07 12:45 ` [Qemu-devel] [PATCH v2 0/6] block: Fixes regarding dataplane and management operations 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=20170410091117.GD4883@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=eswierk@skyportsystems.com \
--cc=famz@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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).