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, dietmar@proxmox.com
Subject: Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command
Date: Mon, 13 May 2013 10:23:27 +0200 [thread overview]
Message-ID: <20130513082327.GA6419@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <518DBC5E.1020700@redhat.com>
Am 11.05.2013 um 05:34 hat Eric Blake geschrieben:
> On 05/08/2013 06:49 AM, Kevin Wolf wrote:
> > Am 29.04.2013 um 09:42 hat Stefan Hajnoczi geschrieben:
> >> @block-backup
> >>
>
> > drive-backup would probably be a more consistent naming. We would then
> > still have block-backup for a future low-level command that doesn't
> > create everything by itself but takes an existing BlockDriverState (e.g.
> > created by blockdev-add).
>
> At least it would match why we named a command 'drive-mirror' instead of
> 'block-mirror'.
>
> Hmm, looking at qapi-schema.json, I wonder if we can rename
> 'BlockdevAction' to 'TransactionAction' as used in the @transaction
> command. It wouldn't change what is sent over the wire in JSON, and
> until we have full introspection, there is no visibility into the type
> name used. Changing the name now would let it be more generic to adding
> future transaction items that are not blockdev related.
Good point, I never realised that once we have schema introspection,
doing such changes is harder. I'm all for it - it's bad enough that we
have specifically block jobs instead of just background jobs, we
shouldn't repeat the same mistake with transactions.
Kevin
next prev parent reply other threads:[~2013-05-13 8:23 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 [this message]
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
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=20130513082327.GA6419@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=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).