From: John Snow <jsnow@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com,
Kashyap Chamarthy <kchamart@redhat.com>,
John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org, mreitz@redhat.com,
vsementsov@parallels.com, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH v6 10/10] qmp-commands.hx: Update the supported 'transaction' operations
Date: Fri, 5 Jun 2015 17:53:08 -0400 [thread overview]
Message-ID: <1433541188-13491-11-git-send-email-jsnow@redhat.com> (raw)
In-Reply-To: <1433541188-13491-1-git-send-email-jsnow@redhat.com>
From: Kashyap Chamarthy <kchamart@redhat.com>
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
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: John Snow <jsnow@redhat.com>
---
qmp-commands.hx | 21 ++++++++++++++++-----
1 file changed, 16 insertions(+), 5 deletions(-)
diff --git a/qmp-commands.hx b/qmp-commands.hx
index 867a21f..cdab36c 100644
--- a/qmp-commands.hx
+++ b/qmp-commands.hx
@@ -1238,11 +1238,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
--
2.1.0
next prev parent reply other threads:[~2015-06-05 21:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 21:52 [Qemu-devel] [PATCH v6 00/10] block: incremental backup transactions John Snow
2015-06-05 21:52 ` [Qemu-devel] [PATCH v6 01/10] qapi: Add transaction support to block-dirty-bitmap operations John Snow
2015-06-05 21:53 ` [Qemu-devel] [PATCH v6 02/10] iotests: add transactional incremental backup test John Snow
2015-06-05 21:53 ` [Qemu-devel] [PATCH v6 03/10] block: rename BlkTransactionState and BdrvActionOps John Snow
2015-06-05 21:53 ` [Qemu-devel] [PATCH v6 04/10] block: re-add BlkTransactionState John Snow
2015-06-05 21:53 ` [Qemu-devel] [PATCH v6 05/10] block: add transactional callbacks feature John Snow
2015-06-24 15:54 ` Max Reitz
2015-06-05 21:53 ` [Qemu-devel] [PATCH v6 06/10] block: add delayed bitmap successor cleanup John Snow
2015-06-05 21:53 ` [Qemu-devel] [PATCH v6 07/10] qmp: Add an implementation wrapper for qmp_drive_backup John Snow
2015-06-05 21:53 ` [Qemu-devel] [PATCH v6 08/10] block: drive_backup transaction callback support John Snow
2015-06-05 21:53 ` [Qemu-devel] [PATCH v6 09/10] iotests: 124 - transactional failure test John Snow
2015-06-05 21:53 ` John Snow [this message]
2015-06-24 15:59 ` [Qemu-devel] [PATCH v6 00/10] block: incremental backup transactions John Snow
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=1433541188-13491-11-git-send-email-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=famz@redhat.com \
--cc=kchamart@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@parallels.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).