From: John Snow <jsnow@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Kashyap Chamarthy" <kchamart@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
famz@redhat.com, QEMU <qemu-devel@nongnu.org>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qmp-commands.hx: Update the supported 'transaction' operations
Date: Mon, 23 Nov 2015 14:02:39 -0500 [thread overview]
Message-ID: <565362CF.908@redhat.com> (raw)
In-Reply-To: <CAJ+F1CJhcY-c=wf-BvcS5E6-2B=CtUzNiPcmZev=qXSKXhH1dw@mail.gmail.com>
On 11/23/2015 01:58 PM, Marc-André Lureau wrote:
> Hi
>
> On Fri, Oct 2, 2015 at 2:12 PM, Kashyap Chamarthy <kchamart@redhat.com> 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.
>
> Isn't the actions limited by the TransactionAction in qapi-schema.json?
>
> { 'union': 'TransactionAction',
> 'data': {
> 'blockdev-snapshot-sync': 'BlockdevSnapshot',
> 'drive-backup': 'DriveBackup',
> + 'blockdev-backup': 'BlockdevBackup',
> 'abort': 'Abort',
> 'blockdev-snapshot-internal-sync': 'BlockdevSnapshotInternal'
> } }
>
> It looks like block-dirty-bitmap-add/clear isn't in the list.
>
> Thanks
>
Maybe at the time. Your codebase is outdated.
##
# @TransactionAction
#
# A discriminated record of operations that can be performed with
# @transaction.
#
# Since 1.1
#
# drive-backup since 1.6
# abort since 1.6
# blockdev-snapshot-internal-sync since 1.7
# blockdev-backup since 2.3
# blockdev-snapshot since 2.5
# block-dirty-bitmap-add since 2.5
# block-dirty-bitmap-clear since 2.5
##
{ 'union': 'TransactionAction',
'data': {
'blockdev-snapshot': 'BlockdevSnapshot',
'blockdev-snapshot-sync': 'BlockdevSnapshotSync',
'drive-backup': 'DriveBackup',
'blockdev-backup': 'BlockdevBackup',
'abort': 'Abort',
'blockdev-snapshot-internal-sync': 'BlockdevSnapshotInternal',
'block-dirty-bitmap-add': 'BlockDirtyBitmapAdd',
'block-dirty-bitmap-clear': 'BlockDirtyBitmap'
} }
>>
>> 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)
>> --
>> 2.4.3
>>
>>
>
>
>
next prev parent reply other threads:[~2015-11-23 19:02 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
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 [this message]
-- 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=565362CF.908@redhat.com \
--to=jsnow@redhat.com \
--cc=famz@redhat.com \
--cc=kchamart@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mreitz@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).