From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: kwolf@redhat.com, jsnow@redhat.com, qemu-devel@nongnu.org,
lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] qmp-commands.hx: Update the supported 'transaction' operations
Date: Mon, 27 Apr 2015 10:47:03 +0100 [thread overview]
Message-ID: <20150427094703.GB15658@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1429864368-15249-1-git-send-email-kchamart@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
On Fri, Apr 24, 2015 at 10:32:47AM +0200, 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
>
> NB: The 'block-dirty-bitmap-add' and 'block-dirty-bitmap-clear' commands
> will be available once the in-review "transactionless incremental
> backup" patch series[1] is merged upstream.
>
> [1] http://lists.nongnu.org/archive/html/qemu-devel/2015-04/msg02161.html
The transactionless incremental backup series has been merged into
block-next and does not contain
block-dirty-bitmap-add/block-dirty-bitmap-clear transactions. They are
part of the transactions series that John Snow sent.
John: Please include this patch in future revisions of your transactions
series.
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-04-27 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 8:32 [Qemu-devel] [PATCH v2] qmp-commands.hx: Update the supported 'transaction' operations Kashyap Chamarthy
2015-04-24 15:52 ` John Snow
2015-04-24 16:20 ` Kashyap Chamarthy
2015-04-24 16:21 ` John Snow
2015-04-24 20:51 ` Eric Blake
2015-04-25 17:18 ` Kashyap Chamarthy
2015-04-27 9:47 ` Stefan Hajnoczi [this message]
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=20150427094703.GB15658@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=jsnow@redhat.com \
--cc=kchamart@redhat.com \
--cc=kwolf@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).