From: Eric Blake <eblake@redhat.com>
To: "Benoît Canet" <benoit@irqsave.net>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, jcody@redhat.com, famz@redhat.com,
armbru@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [RFC V3 7/7] qmp: Allow to take external snapshots on bs graphs node.
Date: Wed, 04 Dec 2013 17:11:26 -0700 [thread overview]
Message-ID: <529FC4AE.6000906@redhat.com> (raw)
In-Reply-To: <1386077165-19577-8-git-send-email-benoit@irqsave.net>
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
On 12/03/2013 06:26 AM, Benoît Canet wrote:
> Signed-off-by: Benoit Canet <benoit@irqsave.net>
> ---
> blockdev.c | 49 +++++++++++++++++++++++++++++++++++++++++--------
> hmp.c | 4 +++-
> qapi-schema.json | 13 ++++++++++---
> qmp-commands.hx | 11 ++++++++++-
> 4 files changed, 64 insertions(+), 13 deletions(-)
>
>
> + if (has_node_name && !has_snapshot_node_name) {
> + error_setg(errp, "New snapshot node name missing");
> + return;
> + }
Why is it okay to omit the node name when passing a device name (which
creates an anonymous node as the new root of the device tree) but not
when passing a node name? Are you trying to guarantee that all
anonymous nodes can be reached from a device name, and that when taking
a snapshot from a node name the new node is not necessarily tied to a
device and must therefore be named?
> -# @device: the name of the device to generate the snapshot from.
> +# Either @device or @node-name must be set but not both.
> +#
> +# @device: #optional the name of the device to generate the snapshot from.
> +#
> +# @node-name: #optional graph node name to generate the snapshot from (Since 1.8)
> #
> # @snapshot-file: the target of the new image. A new file will be created.
> #
> +# @snapshot-node-name: the graph node name of the new image (Since 1.8)
2.0, also mark this one #optional
> +#
> # @format: #optional the format of the snapshot image, default is 'qcow2'.
Unrelated to this patch, but @format is another field worth turning into
an enum instead of an open-coded string.
--
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: 621 bytes --]
next prev parent reply other threads:[~2013-12-05 0:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 13:25 [Qemu-devel] [RFC V3 0/7] Giving names to BlockDriverState graph nodes Benoît Canet
2013-12-03 13:25 ` [Qemu-devel] [RFC V3 1/7] block: Add bs->node_name to hold the name of a bs node of the bs graph Benoît Canet
2013-12-04 23:26 ` Eric Blake
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 2/7] block: Allow the user to define "node-name" option Benoît Canet
2013-12-04 23:33 ` Eric Blake
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 3/7] qapi: Add skeletton of command to query a drive bs graph Benoît Canet
2013-12-04 3:10 ` Fam Zheng
2013-12-04 23:46 ` Eric Blake
2013-12-05 14:24 ` Benoît Canet
2013-12-05 14:38 ` Eric Blake
2013-12-05 14:43 ` Benoît Canet
2013-12-05 14:59 ` Eric Blake
2013-12-05 16:37 ` Benoît Canet
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 4/7] qmp: Allow block_passwd to manipulate bs graph nodes Benoît Canet
2013-12-04 23:56 ` Eric Blake
2013-12-05 14:12 ` Benoît Canet
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 5/7] qmp: Allow block_resize " Benoît Canet
2013-12-05 0:01 ` Eric Blake
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 6/7] block: Create authorizations mechanism for external snapshots Benoît Canet
2013-12-04 3:35 ` Fam Zheng
2013-12-04 5:22 ` Benoît Canet
2013-12-04 3:47 ` Fam Zheng
2013-12-04 5:20 ` Benoît Canet
2013-12-04 6:12 ` Fam Zheng
2013-12-04 6:34 ` Benoît Canet
2013-12-04 7:03 ` Fam Zheng
2013-12-05 14:52 ` Benoît Canet
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 7/7] qmp: Allow to take external snapshots on bs graphs node Benoît Canet
2013-12-04 3:51 ` Fam Zheng
2013-12-04 5:15 ` Benoît Canet
2013-12-05 0:11 ` Eric Blake [this message]
2013-12-05 14:16 ` Benoît Canet
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=529FC4AE.6000906@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=benoit@irqsave.net \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.