From: Max Reitz <mreitz@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qmp-commands.hx: Update the supported 'transaction' operations
Date: Fri, 2 Oct 2015 19:59:48 +0200 [thread overview]
Message-ID: <560EC614.9000109@redhat.com> (raw)
In-Reply-To: <1443787955-19823-1-git-send-email-kchamart@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3217 bytes --]
On 02.10.2015 14:12, Kashyap Chamarthy wrote:
> Although the canonical source of reference for QMP commands is
> qapi-schema.json, for consistency's sake, update qmp-commands.hx to
> state the list of supported transactionable operations, namely:
>
> drive-backup
> blockdev-backup
> blockdev-snapshot-internal-sync
> abort
> block-dirty-bitmap-add
> block-dirty-bitmap-clear
>
> Also update the possible values for the "type" action array.
>
> Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> ---
> In v8 ("v8" because Fam included this as part of a series that is
> in its "v7" edition):
> - Update the possible values for supported 'type' of operation
> ---
> qmp-commands.hx | 29 ++++++++++++++++++++++-------
> 1 file changed, 22 insertions(+), 7 deletions(-)
>
> diff --git a/qmp-commands.hx b/qmp-commands.hx
> index d2ba800d5effaddcae4c437452ef1f67c0aaaaa9..2b52980cfc2f80904a3c7375a382b638e8a51161 100644
> --- a/qmp-commands.hx
> +++ b/qmp-commands.hx
> @@ -1270,11 +1270,22 @@ SQMP
> transaction
> -----------
>
> -Atomically operate on one or more block devices. The only supported operations
> -for now are drive-backup, internal and external snapshotting. A list of
> -dictionaries is accepted, that contains the actions to be performed.
> -If there is any failure performing any of the operations, all operations
> -for the group are abandoned.
> +Atomically operate on one or more block devices. Operations that are
> +currently supported:
> +
> + - drive-backup
> + - blockdev-backup
> + - blockdev-snapshot-sync
> + - blockdev-snapshot-internal-sync
> + - abort
> + - block-dirty-bitmap-add
> + - block-dirty-bitmap-clear
> +
> +Refer to the qemu/qapi-schema.json file for minimum required QEMU
> +versions for these operations. A list of dictionaries is accepted,
> +that contains the actions to be performed. If there is any failure
> +performing any of the operations, all operations for the group are
> +abandoned.
>
> For external snapshots, the dictionary contains the device, the file to use for
> the new snapshot, and the format. The default format, if not specified, is
> @@ -1301,8 +1312,12 @@ it later with qemu-img or other command.
> Arguments:
>
> actions array:
> - - "type": the operation to perform. The only supported
> - value is "blockdev-snapshot-sync". (json-string)
> + - "type": the operation to perform (json-string). Possible
> + values: "drive-backup", "blockdev-backup",
> + "blockdev-snapshot-sync",
> + "blockdev-snapshot-internal-sync",
> + "abort", "block-dirty-bitmap-add",
> + "block-dirty-bitmap-clear"
> - "data": a dictionary. The contents depend on the value
> of "type". When "type" is "blockdev-snapshot-sync":
> - "device": device name to snapshot (json-string)
>
Do you want to extend this list, too? Right now it only contains
parameter information for blockdev-snapshot-sync and
blockdev-snapshot-internal-sync.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-10-02 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 12:12 [Qemu-devel] [PATCH] qmp-commands.hx: Update the supported 'transaction' operations Kashyap Chamarthy
2015-10-02 12:40 ` Eric Blake
2015-10-02 12:51 ` Kashyap Chamarthy
2015-10-02 17:59 ` Max Reitz [this message]
2015-10-12 11:04 ` Kashyap Chamarthy
2015-10-12 13:54 ` Eric Blake
2015-10-12 15:31 ` John Snow
2015-10-12 11:30 ` Kevin Wolf
2015-11-23 18:58 ` Marc-André Lureau
2015-11-23 18:59 ` Marc-André Lureau
2015-11-23 19:02 ` John Snow
-- strict thread matches above, loose matches on Subject: below --
2015-04-23 12:46 Kashyap Chamarthy
2015-04-23 23:07 ` Eric Blake
2015-04-24 7:48 ` Kashyap Chamarthy
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=560EC614.9000109@redhat.com \
--to=mreitz@redhat.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kchamart@redhat.com \
--cc=kwolf@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).