From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
berto@igalia.com, qemu-block@nongnu.org,
Jeff Cody <jcody@redhat.com>,
qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2/4] block: Pause block jobs in bdrv_drain_all
Date: Wed, 8 Apr 2015 11:37:52 +0100 [thread overview]
Message-ID: <20150408103752.GH28835@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1428069921-2957-3-git-send-email-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
On Fri, Apr 03, 2015 at 10:05:19PM +0800, Fam Zheng wrote:
> This is necessary to suppress more IO requests from being generated from
> block job coroutines.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> block.c | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/block.c b/block.c
> index f2f8ae7..00cd91e 100644
> --- a/block.c
> +++ b/block.c
> @@ -2033,6 +2033,16 @@ void bdrv_drain_all(void)
> bool busy = true;
> BlockDriverState *bs;
>
> + QTAILQ_FOREACH(bs, &bdrv_states, device_list) {
> + AioContext *aio_context = bdrv_get_aio_context(bs);
> +
> + aio_context_acquire(aio_context);
> + if (bs->job) {
> + block_job_pause(bs->job);
> + }
> + aio_context_release(aio_context);
> + }
> +
> while (busy) {
> busy = false;
>
> @@ -2044,6 +2054,16 @@ void bdrv_drain_all(void)
> aio_context_release(aio_context);
> }
> }
> +
> + QTAILQ_FOREACH(bs, &bdrv_states, device_list) {
> + AioContext *aio_context = bdrv_get_aio_context(bs);
> +
> + aio_context_acquire(aio_context);
> + if (bs->job) {
> + block_job_resume(bs->job);
> + }
> + aio_context_release(aio_context);
> + }
> }
There is a tiny chance that we pause a job (which actually just sets
job->paused = true but there's no guarantee the job's coroutine reacts
to this) right before it terminates. Then aio_poll() enters the
coroutine one last time and the job terminates.
We then reach the resume portion of bdrv_drain_all() and the job no
longer exists. Hopefully nothing started a new job in the meantime.
bs->job should either be the original block job or NULL.
This code seems under current assumptions, but I just wanted to raise
these issues in case someone sees problems that I've missed.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-04-08 10:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 14:05 [Qemu-devel] [PATCH v2 0/4] Fix "stop" draining block jobs Fam Zheng
2015-04-03 14:05 ` [Qemu-devel] [PATCH v2 1/4] blockjob: Allow nested pause Fam Zheng
2015-04-03 14:13 ` Paolo Bonzini
2015-04-20 17:11 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-04-08 7:25 ` [Qemu-devel] " Alberto Garcia
2015-04-08 10:31 ` Stefan Hajnoczi
2015-04-03 14:05 ` [Qemu-devel] [PATCH v2 2/4] block: Pause block jobs in bdrv_drain_all Fam Zheng
2015-04-07 13:59 ` Alberto Garcia
2015-04-08 10:37 ` Stefan Hajnoczi [this message]
2015-04-08 14:56 ` Alberto Garcia
2015-04-09 10:34 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-04-03 14:05 ` [Qemu-devel] [PATCH v2 3/4] qemu-iotests: Test that "stop" doesn't drain block jobs Fam Zheng
2015-04-07 14:46 ` Alberto Garcia
2015-04-08 10:39 ` Stefan Hajnoczi
2015-04-24 15:43 ` [Qemu-devel] [Qemu-block] " Max Reitz
2015-04-27 5:14 ` Fam Zheng
2015-04-27 11:08 ` Max Reitz
2015-04-03 14:05 ` [Qemu-devel] [PATCH v2 4/4] blockjob: Update function name in comments Fam Zheng
2015-04-07 14:46 ` Alberto Garcia
2015-04-08 10:40 ` [Qemu-devel] [PATCH v2 0/4] Fix "stop" draining block jobs Stefan Hajnoczi
2015-04-20 15:38 ` [Qemu-devel] [Qemu-block] " 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=20150408103752.GH28835@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=berto@igalia.com \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).