qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Fam Zheng <famz@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v7 4/6] qcow2: Add support for ImageInfoSpecific
Date: Tue, 8 Oct 2013 15:55:18 +0200	[thread overview]
Message-ID: <20131008135518.GI25109@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1380703180-27493-5-git-send-email-mreitz@redhat.com>

Am 02.10.2013 um 10:39 hat Max Reitz geschrieben:
> Add a new ImageInfoSpecificQCow2 type as a subtype of ImageInfoSpecific.
> This contains the compatibility level as a string and an optional
> lazy_refcounts boolean (optional means mandatory for compat >= 1.1 and
> not available for compat == 0.10).
> 
> Also, add qcow2_get_specific_info, which returns this information.
> 
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> ---
>  block/qcow2.c    | 19 +++++++++++++++++++
>  qapi-schema.json | 16 ++++++++++++++++
>  2 files changed, 35 insertions(+)
> 
> diff --git a/block/qcow2.c b/block/qcow2.c
> index 4a9888c..396650d 100644
> --- a/block/qcow2.c
> +++ b/block/qcow2.c
> @@ -1810,6 +1810,24 @@ static int qcow2_get_info(BlockDriverState *bs, BlockDriverInfo *bdi)
>      return 0;
>  }
>  
> +static ImageInfoSpecific *qcow2_get_specific_info(BlockDriverState *bs)
> +{
> +    BDRVQcowState *s = bs->opaque;
> +    ImageInfoSpecific *spec_info = g_new0(ImageInfoSpecific, 1);
> +
> +    spec_info->kind = IMAGE_INFO_SPECIFIC_KIND_QCOW2;
> +    spec_info->qcow2 = g_new0(ImageInfoSpecificQCow2, 1);
> +    if (s->qcow_version == 2) {
> +        spec_info->qcow2->compat = g_strdup("0.10");
> +    } else if (s->qcow_version == 3) {
> +        spec_info->qcow2->compat = g_strdup("1.1");
> +        spec_info->qcow2->lazy_refcounts = s->use_lazy_refcounts;

If this function gets reused in a running qemu instance, e.g. from the
monitor, I think the semantics we'd want it to have is to describe the
image file, not the current options (which may have been modified on the
command line or using other monitor commands).

By checking s->compatible_features instead of s->use_lazy_refcounts you
would always return this information.

(Also, how could you leave out this opportunity to use compound
literals?! ;-))

> +        spec_info->qcow2->has_lazy_refcounts = true;
> +    }
> +
> +    return spec_info;
> +}

Kevin

  reply	other threads:[~2013-10-08 13:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02  8:39 [Qemu-devel] [PATCH v7 0/6] Provide additional info through qemu-img info Max Reitz
2013-10-02  8:39 ` [Qemu-devel] [PATCH v7 1/6] qapi: Add ImageInfoSpecific type Max Reitz
2013-10-02  8:39 ` [Qemu-devel] [PATCH v7 2/6] block: Add bdrv_get_specific_info Max Reitz
2013-10-02  8:39 ` [Qemu-devel] [PATCH v7 3/6] block/qapi: Human-readable ImageInfoSpecific dump Max Reitz
2013-10-02  8:39 ` [Qemu-devel] [PATCH v7 4/6] qcow2: Add support for ImageInfoSpecific Max Reitz
2013-10-08 13:55   ` Kevin Wolf [this message]
2013-10-02  8:39 ` [Qemu-devel] [PATCH v7 5/6] qemu-iotests: Discard specific info in _img_info Max Reitz
2013-10-02  8:39 ` [Qemu-devel] [PATCH v7 6/6] qemu-iotests: Additional info from qemu-img info 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=20131008135518.GI25109@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=famz@redhat.com \
    --cc=mreitz@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 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).