From: Kevin Wolf <kwolf@redhat.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] fix qemu_aio_flush
Date: Thu, 04 Jun 2009 13:51:34 +0200 [thread overview]
Message-ID: <4A27B546.3020000@redhat.com> (raw)
In-Reply-To: <20090604112645.GQ25483@random.random>
Andrea Arcangeli schrieb:
> From: Andrea Arcangeli <aarcange@redhat.com>
>
> qemu_aio_wait by invoking the bh or one of the aio completion
> callbacks, could end up submitting new pending aio, breaking the
> invariant that qemu_aio_poll returns only when no pending aio is
> outstanding (possibly a problem for migration as such).
>
> Signed-off-by: Andrea Arcangeli <aarcange@redhat.com>
You mean qemu_aio_flush, not poll. Anyway, the code looks fine.
Acked-by: Kevin Wolf <kwolf@redhat.com>
> ---
>
> diff --git a/aio.c b/aio.c
> index 11fbb6c..dc9b85d 100644
> --- a/aio.c
> +++ b/aio.c
> @@ -103,11 +103,15 @@ void qemu_aio_flush(void)
> do {
> ret = 0;
>
> + /*
> + * If there are pending emulated aio start them now so flush
> + * will be able to return 1.
> + */
> + qemu_aio_wait();
> +
> LIST_FOREACH(node, &aio_handlers, node) {
> ret |= node->io_flush(node->opaque);
> }
> -
> - qemu_aio_wait();
> } while (ret > 0);
> }
>
> diff --git a/qemu-aio.h b/qemu-aio.h
> index 7967829..f262344 100644
> --- a/qemu-aio.h
> +++ b/qemu-aio.h
> @@ -24,9 +24,10 @@ typedef int (AioFlushHandler)(void *opaque);
> * outstanding AIO operations have been completed or cancelled. */
> void qemu_aio_flush(void);
>
> -/* Wait for a single AIO completion to occur. This function will until a
> - * single AIO opeartion has completed. It is intended to be used as a looping
> - * primative when simulating synchronous IO based on asynchronous IO. */
> +/* Wait for a single AIO completion to occur. This function will wait
> + * until a single AIO event has completed and it will ensure something
> + * has moved before returning. This can issue new pending aio as
> + * result of executing I/O completion or bh callbacks. */
> void qemu_aio_wait(void);
>
> /* Register a file descriptor and associated callbacks. Behaves very similarly
>
next prev parent reply other threads:[~2009-06-05 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 16:33 [Qemu-devel] fix bdrv_read/write_em and qemu_aio_flush Andrea Arcangeli
2009-05-30 10:08 ` Christoph Hellwig
2009-05-30 12:17 ` Andrea Arcangeli
2009-06-04 11:26 ` [Qemu-devel] [PATCH] fix qemu_aio_flush Andrea Arcangeli
2009-06-04 11:51 ` Kevin Wolf [this message]
2009-06-05 15:57 ` Christoph Hellwig
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=4A27B546.3020000@redhat.com \
--to=kwolf@redhat.com \
--cc=aarcange@redhat.com \
--cc=hch@lst.de \
--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).