From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] QMP: add snapshot_blkdev command
Date: Mon, 11 Jul 2011 19:50:45 +0200 [thread overview]
Message-ID: <4E1B37F5.9010003@redhat.com> (raw)
In-Reply-To: <20110711133539.5442d454@doriath>
On 07/11/11 18:35, Luiz Capitulino wrote:
> On Fri, 8 Jul 2011 14:00:13 +0200
> Jes.Sorensen@redhat.com wrote:
>
>> From: Jes Sorensen <Jes.Sorensen@redhat.com>
>>
>> Add QMP bits for snapshot_blkdev command. This is the same as
>> snapshot_blkdev in the human monitor. The command is synchronous.
>>
>> In the future async commands and or a break down of the functionality
>> into multiple commands might be added.
>>
>> Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
>> ---
>> qmp-commands.hx | 38 ++++++++++++++++++++++++++++++++++++++
>> 1 files changed, 38 insertions(+), 0 deletions(-)
>>
>> diff --git a/qmp-commands.hx b/qmp-commands.hx
>> index 92c5c3a..eb135c1 100644
>> --- a/qmp-commands.hx
>> +++ b/qmp-commands.hx
>> @@ -694,6 +694,44 @@ Example:
>> EQMP
>>
>> {
>> + .name = "blockdev-snapshot",
>
> blockdev-snapshot-sync.
argh, will fix
>> + .args_type = "device:B,snapshot_file:s?,format:s?",
>> + .params = "device [new-image-file] [format]",
>> + .help = "initiates a live snapshot\n\t\t\t"
>> + "of device. If a new image file is specified, the\n\t\t\t"
>> + "new image file will become the new root image.\n\t\t\t"
>> + "If format is specified, the snapshot file will\n\t\t\t"
>> + "be created in that format. Otherwise the\n\t\t\t"
>> + "snapshot will be internal! (currently unsupported)",
>
> The 'otherwise' part is a bit confusing. You document something as if it were
> supported then you say it's not supported. I recommend to just not document it
> instead.
Ok
>> + .user_print = monitor_user_noop,
>> + .mhandler.cmd_new = do_snapshot_blkdev,
>> + },
>> +
>> +SQMP
>> +blockdev-snapshot-sync
>> +----------------------
>> +
>> +Synchronous snapshot of block device, using snapshot file as target,
>> +if provided.
>
> In QMP only this text is used, the text in '.help' is discarded. Please,
> move all command documentation here.
If .help isn't used, then please remove it from the struct. It is really
pointless to keep carrying both around.
>> +
>> +Arguments:
>> +
>> +- "device": device name to snapshot (json-string)
>> +- "snapshot_file": name of new image file (json-string)
>> +- "format": format of new image (json-string)
>> +
>> +Example:
>> +
>> +-> { "execute": "blockdev-snapshot", "arguments": { "device": "ide-hd0",
>> + "snapshot_file":
>
> We are trying to standardize the use of hyphen in QMP.
Sorry, but I haven't got a clue what you mean here.
Jes
next prev parent reply other threads:[~2011-07-11 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 12:00 [Qemu-devel] [PATCH 0/1] QMP command for snapshot_blkdev Jes.Sorensen
2011-07-08 12:00 ` [Qemu-devel] [PATCH 1/1] QMP: add snapshot_blkdev command Jes.Sorensen
2011-07-11 16:35 ` Luiz Capitulino
2011-07-11 17:50 ` Jes Sorensen [this message]
2011-07-11 17:58 ` Luiz Capitulino
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=4E1B37F5.9010003@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).