qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Fam Zheng <famz@redhat.com>,
	qemu-devel@nongnu.org, Wenchao Xia <xiawenc@linux.vnet.ibm.com>,
	imain@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>,
	pbonzini@redhat.com, lcapitulino@redhat.com, dietmar@proxmox.com
Subject: Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command
Date: Mon, 13 May 2013 15:09:31 +0200	[thread overview]
Message-ID: <20130513130931.GC6419@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <5190E30E.40005@redhat.com>

Am 13.05.2013 um 14:56 hat Eric Blake geschrieben:
> On 05/13/2013 02:28 AM, Kevin Wolf wrote:
> 
> >>> +{ 'command': 'block-backup',
> >>> +  'data': { 'device': 'str', 'target': 'str', '*format': 'str',
> >>
> >> Hmm - wondering if we should add an enum type for supported disk formats
> >> instead of using free-form strings.  The wire representation would be
> >> the same, and now's the time to do it before we add introspection (it's
> >> more than just this command impacted).
> > 
> > And ideally we shouldn't make it a static list that contains every
> > format for which qemu has some code, but only those that are actually
> > compiled in. (Hm, and probably not protocols?)
> > 
> > Luiz, any idea how to do something like this, a QAPI enum with values
> > that are determined at runtime? Especially with respect to the coming
> > schema introspection?
> 
> Or maybe we make the 'enum' list ALL possible types, but then add a
> query-* command that returns an array of only those enum values that are
> supported.  Introspection would see all types, but the query command
> would be the useful variant that is runtime-dependent.

Then is there any advantage in making it an enum in the first place? Can
libvirt really make use of the information "this qemu version could have
been compiled with VHDX support, but it hasn't"?

Kevin

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

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29  7:42 [Qemu-devel] [PATCH v2 0/3] block: block-backup live backup command Stefan Hajnoczi
2013-04-29  7:42 ` [Qemu-devel] [PATCH v2 1/3] block: add basic backup support to block driver Stefan Hajnoczi
2013-05-08 12:39   ` Kevin Wolf
2013-05-08 15:43     ` Paolo Bonzini
2013-05-14  8:51     ` Stefan Hajnoczi
2013-05-14 13:24     ` Stefan Hajnoczi
2013-05-14 13:43       ` Kevin Wolf
2013-05-14 15:12         ` Stefan Hajnoczi
2013-05-30  3:37   ` Fam Zheng
2013-05-30 12:27     ` Stefan Hajnoczi
2013-04-29  7:42 ` [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command Stefan Hajnoczi
2013-05-08 12:49   ` Kevin Wolf
2013-05-11  3:34     ` Eric Blake
2013-05-11  8:02       ` Paolo Bonzini
2013-05-13  8:23       ` Kevin Wolf
2013-05-14  8:44     ` Stefan Hajnoczi
2013-05-11  4:02   ` Eric Blake
2013-05-13  8:28     ` Kevin Wolf
2013-05-13 12:56       ` Eric Blake
2013-05-13 13:09         ` Kevin Wolf [this message]
2013-05-13 13:18           ` Luiz Capitulino
2013-05-13 14:14             ` Eric Blake
2013-05-13 14:27               ` Kevin Wolf
2013-05-13 14:50                 ` Eric Blake
2013-05-14  2:18                   ` Wenchao Xia
2013-05-14  8:48     ` Stefan Hajnoczi
2013-04-29  7:42 ` [Qemu-devel] [PATCH v2 3/3] qemu-iotests: add 054 block-backup test case 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=20130513130931.GC6419@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=dietmar@proxmox.com \
    --cc=eblake@redhat.com \
    --cc=famz@redhat.com \
    --cc=imain@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).