qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
	qemu-devel@nongnu.org, Ian Main <imain@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	dietmar@proxmox.com
Subject: Re: [Qemu-devel] [PATCH 0/3] block: block-backup live backup command
Date: Tue, 23 Apr 2013 18:57:36 +0200	[thread overview]
Message-ID: <5176BD80.5070401@redhat.com> (raw)
In-Reply-To: <5176BB9F.5060003@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Il 23/04/2013 18:49, Eric Blake ha scritto:
> Based on today's phone call, it sounds like this would mean adding 
> optional parameters to the QMP command.  We already did that for 
> drive-mirror (1.4 has more parameters than 1.3), but without a way
> to introspect when those parameters are available, the new
> parameters aren't quite as useful.  So we don't repeat that
> mistake, we need to decide whether this should still go into 1.5
> with a plan of adding parameters for 1.6, or whether we should add
> a counterpart query-* command that makes it easy to determine how
> much of block-backup is supported, or [your suggestion here]....

... libvirt can omit the optional parameters if they match the default
and just try executing the command.  If it gets an error, it just
reports it.

That is, instead of

     dictionary = json_object_new()
     if (has_capability)
         add argument to JSON dictionary
     else if (argument != default)
         return error

     send JSON dictionary via QMP

do this

     dictionary = json_object_new()
     if (argument != default)
         add argument to JSON dictionary
     send JSON dictionary via QMP

Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRdr2AAAoJEBvWZb6bTYbydkAP/0EegweCJX37/XIJ9vtYy4c1
RdS1Jkg/t+KNfsmUp/Qs0JpYbbxhLbbsM9pboKc1LU2Mv5HZd2koibIYNOwTTN3q
y2A/4Ecr8A+Q9pv8mblTb8HFea3FDNwtBugTQG7LM/CywYdAk6tg4qZ/0NEXVAPA
XEmR0RXRP0ln52f/fByFuq2czg4VvXqygKeBtRJ20ROeUCNpNxYDjiBX03I/4OE8
B1iTkMy7fJwKoc34tOPZ04IzNIRI/Zxtl2my5j3wx7iheYUXNAYPrKpSKXwqYj3g
x+jRe7A/QxUZpBTmIynBmDvOxut8ZaLqeWAHYWlcNZameWGSZJgsav5hMjaOVlS3
Kk0Tkm4rrgSYuzC+vhttvGaj9iacnRaG6IMmwyfq1TFcETXLH6ILt8sCxoO5dpHp
XetKnEF4m1zmQDXceMbFLRZ3eOKMjwObf6QQIjLkrs/0Xc+T+GfsqUdN6ylY17Rk
s6Jsx5ICbS4IUJlktkVv/U9n4VD7y9IBwRlglKgj86noHPFFkb/Z+C0cW8Zkwej/
ZsrjXTNB1abI6/X11PvoaqEnFauaradbtMfRbEmDMhBi+CoBZ9ps578OSn9+x1rn
j+WYup9Z5qnDO+BvG+tDElaY6qQUR4ZaGOKo05ODjXkPd83Jn/pOjD2ioaa1dybY
KP+0EDFS6SwiSX5jsoei
=C9uD
-----END PGP SIGNATURE-----

  reply	other threads:[~2013-04-23 16:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 16:25 [Qemu-devel] [PATCH 0/3] block: block-backup live backup command Stefan Hajnoczi
2013-04-23 16:25 ` [Qemu-devel] [PATCH 1/3] block: add basic backup support to block driver Stefan Hajnoczi
2013-04-23 16:25 ` [Qemu-devel] [PATCH 2/3] block: add block_backup QMP command Stefan Hajnoczi
2013-04-26 22:52   ` Eric Blake
2013-04-26 22:53     ` Eric Blake
2013-04-26 22:58   ` Eric Blake
2013-04-29  7:21     ` Stefan Hajnoczi
2013-04-29  9:27       ` Paolo Bonzini
2013-04-29 15:51         ` Eric Blake
2013-05-01 11:55           ` Stefan Hajnoczi
2013-04-23 16:25 ` [Qemu-devel] [PATCH 3/3] qemu-iotests: add 054 block-backup test case Stefan Hajnoczi
2013-04-23 16:49 ` [Qemu-devel] [PATCH 0/3] block: block-backup live backup command Eric Blake
2013-04-23 16:57   ` Paolo Bonzini [this message]
2013-04-24  7:41   ` Stefan Hajnoczi
2013-04-24 12:44     ` Eric Blake
2013-04-27  5:37 ` Wenchao Xia
2013-04-29  7:22   ` 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=5176BD80.5070401@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dietmar@proxmox.com \
    --cc=eblake@redhat.com \
    --cc=famz@redhat.com \
    --cc=imain@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 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).