From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 17/20] qemu-io: Use bdrv_parse_cache_mode() in reopen_f()
Date: Tue, 29 Mar 2016 12:16:40 +0200 [thread overview]
Message-ID: <20160329101640.GC4600@noname.redhat.com> (raw)
In-Reply-To: <56F6F995.1040906@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2339 bytes --]
Am 26.03.2016 um 22:05 hat Max Reitz geschrieben:
> On 18.03.2016 19:21, Kevin Wolf wrote:
> > We must forbid changing the WCE flag in bdrv_reopen() in the same patch,
> > as otherwise the behaviour would change so that the flag takes
> > precedence over the explicitly specified option.
> >
> > The correct value of the WCE flag depends on the BlockBackend user (e.g.
> > guest device) and isn't a decision that the QMP client makes, so this
> > change is what we want.
> >
> > Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> > ---
> > block.c | 18 ++++++------------
> > qemu-io-cmds.c | 14 +++++++++++++-
> > tests/qemu-iotests/142 | 2 +-
> > tests/qemu-iotests/142.out | 2 +-
> > 4 files changed, 21 insertions(+), 15 deletions(-)
> >
>
> [...]
>
> > diff --git a/qemu-io-cmds.c b/qemu-io-cmds.c
> > index e929d24..7de3754 100644
> > --- a/qemu-io-cmds.c
> > +++ b/qemu-io-cmds.c
>
> [...]
>
> > @@ -2136,14 +2137,25 @@ static int reopen_f(BlockBackend *blk, int argc, char **argv)
> > return qemuio_command_usage(&reopen_cmd);
> > }
> >
> > + if (writethrough != blk_enable_write_cache(blk) &&
> > + blk_get_attached_dev(blk))
> > + {
> > + error_report("Cannot change cache.writeback: Device attached");
> > + qemu_opts_reset(&reopen_opts);
> > + return 0;
> > + }
> > +
> > qopts = qemu_opts_find(&reopen_opts, NULL);
> > opts = qopts ? qemu_opts_to_qdict(qopts, NULL) : NULL;
> > qemu_opts_reset(&reopen_opts);
> >
> > + flags |= blk_enable_write_cache(blk) ? BDRV_O_CACHE_WB : 0;
>
> Shouldn't this be bdrv_enable_write_cache(bs)?
>
> With blk_enable_write_cache(blk), reopening a non-WB BB should always
> fail because bdrv_reopen_multiple() accuses us of trying to change the
> WB mode (whereas we really don't want to change the BDS's mode).
bdrv_enable_write_cache() is only a wrapper around
blk_enable_write_cache(), so that wouldn't make any difference. It also
means that bdrv_reopen() checks the cache mode of the BlockBackend
rather than always returning true. This line exists precisely to avoid
the error message you mention.
And as you noticed, the line goes away anyway when BDRV_O_CACHE_WB is
removed later in the series.
Kevin
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-03-29 10:16 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 18:21 [Qemu-devel] [PATCH 00/20] block: Implement writethrough in BlockBackend Kevin Wolf
2016-03-18 18:21 ` [Qemu-devel] [PATCH 01/20] block: Add bdrv_parse_cache_mode() Kevin Wolf
2016-03-26 17:05 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 02/20] qemu-nbd: Call blk_set_enable_write_cache() explicitly Kevin Wolf
2016-03-26 17:09 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 03/20] qemu-io: " Kevin Wolf
2016-03-26 17:18 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 04/20] qemu-img: Expand all BDRV_O_FLAGS uses Kevin Wolf
2016-03-26 17:34 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 05/20] qemu-img: Call blk_set_enable_write_cache() explicitly Kevin Wolf
2016-03-26 17:54 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 06/20] xen_disk: " Kevin Wolf
2016-03-22 11:08 ` Stefano Stabellini
2016-03-26 17:59 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 07/20] block: blockdev_init(): " Kevin Wolf
2016-03-26 18:13 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 08/20] block: Always set writeback mode in blk_new_open() Kevin Wolf
2016-03-26 18:36 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 09/20] block: Handle flush error in bdrv_pwrite_sync() Kevin Wolf
2016-03-26 18:46 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 10/20] block: Move enable_write_cache to BB level Kevin Wolf
2016-03-26 19:54 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 11/20] block/qapi: Use blk_enable_write_cache() Kevin Wolf
2016-03-26 20:14 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 12/20] block: Introduce bdrv_co_writev_flags() Kevin Wolf
2016-03-26 20:24 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 13/20] iscsi: Support BDRV_REQ_FUA Kevin Wolf
2016-03-26 20:33 ` Max Reitz
2016-03-26 20:44 ` Max Reitz
2016-03-29 11:02 ` Kevin Wolf
2016-03-18 18:21 ` [Qemu-devel] [PATCH 14/20] nbd: " Kevin Wolf
2016-03-26 20:46 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 15/20] raw: " Kevin Wolf
2016-03-26 20:49 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 16/20] block: Use bdrv_parse_cache_mode() in drive_init() Kevin Wolf
2016-03-26 20:53 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 17/20] qemu-io: Use bdrv_parse_cache_mode() in reopen_f() Kevin Wolf
2016-03-26 21:05 ` Max Reitz
2016-03-29 10:16 ` Kevin Wolf [this message]
2016-03-18 18:21 ` [Qemu-devel] [PATCH 18/20] block: Remove bdrv_parse_cache_flags() Kevin Wolf
2016-03-26 21:06 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 19/20] block: Remove BDRV_O_CACHE_WB Kevin Wolf
2016-03-26 21:23 ` Max Reitz
2016-03-18 18:21 ` [Qemu-devel] [PATCH 20/20] block: Remove bdrv_(set_)enable_write_cache() Kevin Wolf
2016-03-26 21:25 ` Max Reitz
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=20160329101640.GC4600@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=mreitz@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).