From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org, mreitz@redhat.com,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 2/2] blockjob: Fix hang in block_job_finish_sync
Date: Thu, 28 Jan 2016 12:07:22 +0000 [thread overview]
Message-ID: <20160128120722.GH7206@stefanha-x1.localdomain> (raw)
In-Reply-To: <56A9DAEE.7060206@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2049 bytes --]
On Thu, Jan 28, 2016 at 10:10:06AM +0100, Paolo Bonzini wrote:
>
>
> On 28/01/2016 08:02, Fam Zheng wrote:
> >
> > This is because the aio_poll() only processes the AIO context of bs
> > which has no more work to do, while the main loop BH that is scheduled
> > for setting the job->completed flag is never processed.
> >
> > Fix this by adding a "ctx" pointer in BlockJob structure, to track which
> > context to poll for the block job to make progress. Its value is set to
> > the BDS context at block job creation, until
> > block_job_coroutine_complete() is called by the block job coroutine.
> > After that point, the block job's work is deferred to main loop BH.
> >
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > ---
> > blockjob.c | 4 +++-
> > include/block/blockjob.h | 2 ++
> > 2 files changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/blockjob.c b/blockjob.c
> > index 4b16720..4ea1ce0 100644
> > --- a/blockjob.c
> > +++ b/blockjob.c
> > @@ -74,6 +74,7 @@ void *block_job_create(const BlockJobDriver *driver, BlockDriverState *bs,
> > job->opaque = opaque;
> > job->busy = true;
> > job->refcnt = 1;
> > + job->ctx = bdrv_get_aio_context(bs);
>
> Can the context change if dataplane is started/stopped in the middle of
> a job? (For example if you start migration). Perhaps job->ctx == NULL
> could mean "use bdrv_get_aio_context(bs)".
Yes, it can change.
Normally a block job doesn't need to know its AioContext since the
coroutine only runs from inside the AioContext anyway.
Perhaps it's easier to make this special case explicit with a flag in
job->deferred_to_main_loop so the synchronous wait can do:
while (!job->completed) {
AioContext *ctx = job->deferred_to_main_loop ?
qemu_get_aio_context() :
bdrv_get_aio_context(bs);
aio_poll(ctx, true);
}
That way there's no need to store a possibly stale AioContext pointer.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-01-28 12:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 7:02 [Qemu-devel] [PATCH 0/2] blockjob: Fix dead loop with block_job_finish_sync on dataplane disks Fam Zheng
2016-01-28 7:02 ` [Qemu-devel] [PATCH 1/2] blockjob: Rename block_job_defer_to_main_loop Fam Zheng
2016-01-28 11:53 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2016-01-28 13:14 ` Fam Zheng
2016-01-28 7:02 ` [Qemu-devel] [PATCH 2/2] blockjob: Fix hang in block_job_finish_sync Fam Zheng
2016-01-28 9:10 ` Paolo Bonzini
2016-01-28 10:57 ` Fam Zheng
2016-01-28 12:07 ` Stefan Hajnoczi [this message]
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=20160128120722.GH7206@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=famz@redhat.com \
--cc=kwolf@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).