From: Eric Blake <eblake@redhat.com>
To: "Benoît Canet" <benoit.canet@gmail.com>
Cc: aliguori@us.ibm.com, "Benoît Canet" <benoit@irqsave.net>,
qemu-devel@nongnu.org, pbonzini@redhat.com,
xiawenc@linux.vnet.ibm.com, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 2/3] qapi: Add ImageInfo.
Date: Wed, 15 Aug 2012 10:17:54 -0600 [thread overview]
Message-ID: <502BCBB2.4030301@redhat.com> (raw)
In-Reply-To: <1345042466-31743-3-git-send-email-benoit@irqsave.net>
[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]
On 08/15/2012 08:54 AM, Benoît Canet wrote:
> Signed-off-by: Benoit Canet <benoit@irqsave.net>
> ---
> qapi-schema.json | 33 +++++++++++++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
>
> diff --git a/qapi-schema.json b/qapi-schema.json
> index 8d4df19..488da90 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -150,6 +150,39 @@
> 'vm-clock-sec': 'int' } }
>
> ##
> +# @ImageInfo:
> +#
> +# Information about a QEMU image file
> +#
> +# @filename: name of the image file
> +#
> +# @format: format of the image file
> +#
> +# @dirty-flag: true if image is not cleanly closed
> +#
> +# @cluster-size: size of a cluster in bytes
> +#
> +# @encrypted: true if the image is encrypted
> +#
> +# @actual-size: actual size on disk in bytes of the image
> +#
> +# @virtual-size: maximum capacity in bytes of the image
> +#
> +# @backing-filename: name of the backing file
Should this be #optional, in the case where there is no backing file?
Missing @backing-filename-format, when that is recorded (as long as
we're going for machine-parseable, print everything useful, even if
qemu-img info doesn't print it right now). Definitely #optional, since
it won't be present when @backing-filename is missing, and even when a
backing file name is present, the format might not have been recorded.
> +#
> +# @snapshots: list of VM snapshots
Should this be #optional, in the case where there are no snapshots?
> +#
> +# Since: 1.3
So no way it will make 1.2 hard freeze today :)
--
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: 620 bytes --]
next prev parent reply other threads:[~2012-08-15 16:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 14:54 [Qemu-devel] [PATCH 0/3] Add JSON output to qemu-img info Benoît Canet
2012-08-15 14:54 ` [Qemu-devel] [PATCH 1/3] qapi: Add SnapshotInfo Benoît Canet
2012-08-15 17:58 ` Luiz Capitulino
2012-08-15 18:18 ` Benoît Canet
2012-08-15 18:04 ` Eric Blake
2012-08-15 18:14 ` Benoît Canet
2012-08-15 14:54 ` [Qemu-devel] [PATCH 2/3] qapi: Add ImageInfo Benoît Canet
2012-08-15 16:17 ` Eric Blake [this message]
2012-08-15 16:49 ` Benoît Canet
2012-08-15 17:47 ` Eric Blake
2012-08-15 14:54 ` [Qemu-devel] [PATCH 3/3] qemu-img: Add json output option to the info command Benoît Canet
2012-08-15 16:23 ` Eric Blake
2012-08-15 16:39 ` Benoît Canet
2012-08-15 18:16 ` Luiz Capitulino
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=502BCBB2.4030301@redhat.com \
--to=eblake@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=benoit.canet@gmail.com \
--cc=benoit@irqsave.net \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=xiawenc@linux.vnet.ibm.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).