From: Eric Blake <eblake@redhat.com>
To: Wen Congyang <wency@cn.fujitsu.com>,
qemu devel <qemu-devel@nongnu.org>, Fam Zheng <famz@redhat.com>,
Max Reitz <mreitz@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
zhanghailiang <zhang.zhanghailiang@huawei.com>,
qemu block <qemu-block@nongnu.org>,
Jiang Yunhong <yunhong.jiang@intel.com>,
Dong Eddie <eddie.dong@intel.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Michael R. Hines" <mrhines@linux.vnet.ibm.com>,
Gonglei <arei.gonglei@huawei.com>,
Yang Hongyang <yanghy@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH v10 01/10] allow writing to the backing file
Date: Fri, 9 Oct 2015 13:07:30 -0600 [thread overview]
Message-ID: <56181072.1020805@redhat.com> (raw)
In-Reply-To: <1443161858-20533-2-git-send-email-wency@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]
On 09/25/2015 12:17 AM, Wen Congyang wrote:
> For block replication, we have such backing chain:
> secondary disk <-- hidden disk <-- active disk
> secondary disk is top BDS(use bacing reference), so it can be opened in
s/BDS(use bacing/BDS (use backing/
> read-write mode. But hidden disk is read only, and we need to write to
> hidden disk(backup job will write data to it).
s/disk(/disk (/
>
> TODO: support opening backing file in read-write mode if the BDS is
> created by QMP command blockdev-add.
>
> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
> ---
> block.c | 41 ++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 40 insertions(+), 1 deletion(-)
>
I really don't like this patch. We are able to automatically (re-)open
backing files for write during block-commit, without having to expose a
knob to the user then, so exposing a knob to the user here feels wrong.
> +#define ALLOW_WRITE_BACKING_FILE "allow-write-backing-file"
> +static QemuOptsList backing_file_opts = {
> + .name = "backing_file",
> + .head = QTAILQ_HEAD_INITIALIZER(backing_file_opts.head),
> + .desc = {
> + {
> + .name = ALLOW_WRITE_BACKING_FILE,
> + .type = QEMU_OPT_BOOL,
> + .help = "allow writes to backing file",
> + },
And even if we DO need this knob (which I doubt), you need corresponding
documentation of the knob in qapi/block-core.json, since we are trying
to keep the command line and QMP in sync when it comes to adding new
options.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-10-09 19:07 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 6:17 [Qemu-devel] [PATCH v10 00/10] Block replication for continuous checkpoints Wen Congyang
2015-09-25 6:17 ` [Qemu-devel] [PATCH v10 01/10] allow writing to the backing file Wen Congyang
2015-10-09 19:07 ` Eric Blake [this message]
2015-10-30 5:49 ` Wen Congyang
2015-09-25 6:17 ` [Qemu-devel] [PATCH v10 02/10] Backup: clear all bitmap when doing block checkpoint Wen Congyang
2015-10-09 19:09 ` Eric Blake
2015-10-12 13:45 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-10-13 9:13 ` Wen Congyang
2015-10-14 14:12 ` Stefan Hajnoczi
2015-09-25 6:17 ` [Qemu-devel] [PATCH v10 03/10] Allow creating backup jobs when opening BDS Wen Congyang
2015-09-25 6:17 ` [Qemu-devel] [PATCH v10 04/10] block: make bdrv_put_ref_bh_schedule() as a public API Wen Congyang
2015-09-25 6:17 ` [Qemu-devel] [PATCH v10 05/10] docs: block replication's description Wen Congyang
2015-09-25 6:17 ` [Qemu-devel] [PATCH v10 06/10] Add new block driver interfaces to control block replication Wen Congyang
2015-09-25 6:17 ` [Qemu-devel] [PATCH v10 07/10] quorum: implement block driver interfaces for " Wen Congyang
2015-09-25 6:17 ` [Qemu-devel] [PATCH v10 08/10] Implement new driver " Wen Congyang
2015-10-12 16:25 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-10-13 8:59 ` Wen Congyang
2015-10-13 9:41 ` Fam Zheng
2015-10-13 9:46 ` Wen Congyang
2015-10-13 10:12 ` Fam Zheng
2015-10-14 0:55 ` Wen Congyang
2015-10-12 16:27 ` Stefan Hajnoczi
2015-10-13 9:08 ` Wen Congyang
2015-10-14 14:27 ` Stefan Hajnoczi
2015-10-15 2:19 ` Wen Congyang
2015-10-15 14:55 ` Stefan Hajnoczi
2015-10-16 0:52 ` Wen Congyang
2015-10-16 2:22 ` Wen Congyang
2015-10-16 11:37 ` Stefan Hajnoczi
2015-10-27 2:57 ` Wen Congyang
2015-10-27 14:41 ` Stefan Hajnoczi
2015-10-12 16:31 ` Stefan Hajnoczi
2015-10-13 9:09 ` Wen Congyang
2015-09-25 6:17 ` [Qemu-devel] [PATCH v10 09/10] support replication driver in blockdev-add Wen Congyang
2015-10-09 14:40 ` Eric Blake
2015-09-25 6:17 ` [Qemu-devel] [PATCH v10 10/10] Add a new API to start/stop replication, do checkpoint to all BDSes Wen Congyang
2015-10-07 6:39 ` [Qemu-devel] [PATCH v10 00/10] Block replication for continuous checkpoints Wen Congyang
2015-10-09 12:52 ` 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=56181072.1020805@redhat.com \
--to=eblake@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=dgilbert@redhat.com \
--cc=eddie.dong@intel.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=mrhines@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wency@cn.fujitsu.com \
--cc=yanghy@cn.fujitsu.com \
--cc=yunhong.jiang@intel.com \
--cc=zhang.zhanghailiang@huawei.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).