qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/6 v11] add-cow: support snapshot_blkde
Date: Thu, 2 Aug 2012 11:37:48 +0100	[thread overview]
Message-ID: <CAJSP0QUuXtWvmAK2ZvQPsLNCAo0mjzbPpSpj4HKo7+V2VkDo7g@mail.gmail.com> (raw)
In-Reply-To: <CAGrFBsjMJpjBgpX++_hx0+RPGiy-YSEMd3GNAxF2L++NZUew4g@mail.gmail.com>

On Thu, Aug 2, 2012 at 8:28 AM, Dong Xu Wang <wdongxu@linux.vnet.ibm.com> wrote:
> On Wed, Aug 1, 2012 at 11:37 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
>> On Tue, Jul 31, 2012 at 5:51 PM, Dong Xu Wang
>> <wdongxu@linux.vnet.ibm.com> wrote:
>>> add-cow will let raw file support snapshot_blkdev indirectly.
>>>
>>> Signed-off-by: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
>>> ---
>>>  blockdev.c              |   45 +++++++++++++++++++++++++++++++++++++--------
>>>  docs/live-block-ops.txt |   11 ++++++++++-
>>>  2 files changed, 47 insertions(+), 9 deletions(-)
>>
>> This patch would need to update qapi-schema.json and qmp-commands.hx
>> to make use of the new arguments.
>>
>> I don't think QEMU compiles cleanly after this patch.  It's important
>> to keep the build clean after every patch so that git-bisect(1) can be
>> used (if you hit a broken build during a bisect it makes things
>> harder).
>>
>> However, I think the QMP/HMP changes should not be included in this
>> series unless you are sure the interface is stable.  When you convert
>> QEMUOptionsParameter will transaction or snapshot-blkdev-sync change?
>> If so, please only send the add-cow image format and leave the QMP/HMP
>> changes until you have the QemuOpts solution.
>
> Ah, yes, sorry, the patch must be compiled with 5/6, HMP  now works like:
> [-n] device [new-image-file] [format] [image-file] [image-format]
>
> snapshot_blockdev /dev/ide-id0 1.add-cow add-cow t.raw raw
>
> Also qmp's args_type:
> .args_type  = "device:B,snapshot-file:s,format:s?,mode:s?,image-file:s?,image-format:s?",
>
> Before  converting QEMUOptionsParameter, can the code be like this?

I think it's cleanest to submit just the image format without
snapshot_blockdev interface changes.  It's definitely not a good idea
to temporarily change the QMP/HMP interface if the
QEMUOptionsParameter conversion will change it again.

Stefan

  reply	other threads:[~2012-08-02 10:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 16:51 [Qemu-devel] [PATCH 1/6 v11] docs: spec for add-cow file format Dong Xu Wang
2012-07-31 16:51 ` [Qemu-devel] [PATCH 2/6 v11 v11] block: make some functions public Dong Xu Wang
2012-08-01 13:53   ` Eric Blake
2012-08-02  7:10     ` Dong Xu Wang
2012-08-01 14:01   ` Stefan Hajnoczi
2012-08-02  7:11     ` Dong Xu Wang
2012-07-31 16:51 ` [Qemu-devel] [PATCH 3/6] add-cow file format Dong Xu Wang
2012-08-01 13:57   ` Eric Blake
2012-08-01 14:14     ` Stefan Hajnoczi
2012-08-01 14:21       ` Kevin Wolf
2012-08-02  7:20     ` Dong Xu Wang
2012-08-01 15:31   ` Stefan Hajnoczi
2012-08-02  7:20     ` Dong Xu Wang
2012-07-31 16:51 ` [Qemu-devel] [PATCH 4/6 v11] add-cow: support snapshot_blkde Dong Xu Wang
2012-08-01 15:37   ` Stefan Hajnoczi
2012-08-02  7:28     ` Dong Xu Wang
2012-08-02 10:37       ` Stefan Hajnoczi [this message]
2012-07-31 16:51 ` [Qemu-devel] [PATCH 5/6 v11] add-cow: hmp and qmp interface Dong Xu Wang
2012-07-31 16:51 ` [Qemu-devel] [PATCH 6/6 v11] add-cow: support qemu-iotests Dong Xu Wang
2012-08-01 13:51 ` [Qemu-devel] [PATCH 1/6 v11] docs: spec for add-cow file format Eric Blake
2012-08-02  7:03   ` Dong Xu Wang
2012-08-01 13:55 ` Stefan Hajnoczi
2012-08-02  7:09   ` Dong Xu Wang
2012-08-02 10:44     ` Stefan Hajnoczi
2012-08-03  5:56       ` Dong Xu Wang
2012-08-03  8:26         ` Stefan Hajnoczi
2012-08-06  2:05           ` Dong Xu Wang

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=CAJSP0QUuXtWvmAK2ZvQPsLNCAo0mjzbPpSpj4HKo7+V2VkDo7g@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wdongxu@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).