From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] raw-posix: Make aio=native option binding
Date: Tue, 15 Dec 2015 13:26:33 +0100 [thread overview]
Message-ID: <567006F9.3070203@de.ibm.com> (raw)
In-Reply-To: <1450176143-13265-1-git-send-email-kwolf@redhat.com>
On 12/15/2015 11:42 AM, Kevin Wolf wrote:
> Subject: [PATCH] raw-posix: Make aio=native option binding
bike-shedding, but is there a better wording for the subject line,
e.g. something like
raw-posix: error out on invalid configurations for aio=native
or something like that
> Traditionally, aio=native was treated as an advice that could simply be
> ignored if an error occurs while initialising Linux AIO or the feature
> wasn't compiled in. This behaviour was deprecated in commit 96518254
> (qemu 2.3; error during init) and commit 1501ecc1 (qemu 2.5; not
> compiled in).
>
> This patch changes raw-posix to error out in these cases instead of
> printing a deprecation warning.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> block/raw-posix.c | 20 ++++++++------------
> 1 file changed, 8 insertions(+), 12 deletions(-)
>
> diff --git a/block/raw-posix.c b/block/raw-posix.c
> index d9162fd..cb26dcb 100644
> --- a/block/raw-posix.c
> +++ b/block/raw-posix.c
> @@ -500,21 +500,17 @@ static int raw_open_common(BlockDriverState *bs, QDict *options,
> goto fail;
> }
> if (!s->use_aio && (bdrv_flags & BDRV_O_NATIVE_AIO)) {
> - error_printf("WARNING: aio=native was specified for '%s', but "
> - "it requires cache.direct=on, which was not "
> - "specified. Falling back to aio=threads.\n"
> - " This will become an error condition in "
> - "future QEMU versions.\n",
> - bs->filename);
> + error_setg(errp, "aio=native was specified, but it requires "
> + "cache.direct=on, which was not specified.");
> + ret = -EINVAL;
> + goto fail;
In the real life this is probably the right thing to do.
On the other hand its a Linux kernel implementation detail that aio does
only work with O_DIRECT. But anyway, if Linux aio gets fixed we can
change QEMU again.
> }
> #else
> if (bdrv_flags & BDRV_O_NATIVE_AIO) {
> - error_printf("WARNING: aio=native was specified for '%s', but "
> - "is not supported in this build. Falling back to "
> - "aio=threads.\n"
> - " This will become an error condition in "
> - "future QEMU versions.\n",
> - bs->filename);
> + error_setg(errp, "aio=native was specified, but is not supported "
> + "in this build.");
> + ret = -EINVAL;
> + goto fail;
We certainly want to error out in this case.
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
next prev parent reply other threads:[~2015-12-15 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 10:42 [Qemu-devel] [PATCH] raw-posix: Make aio=native option binding Kevin Wolf
2015-12-15 12:26 ` Christian Borntraeger [this message]
2015-12-16 3:20 ` [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=567006F9.3070203@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=kwolf@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).