From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51928) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YlgLP-00052K-AQ for qemu-devel@nongnu.org; Fri, 24 Apr 2015 12:20:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YlgLM-0005la-2n for qemu-devel@nongnu.org; Fri, 24 Apr 2015 12:20:47 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58038) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YlgLL-0005je-S0 for qemu-devel@nongnu.org; Fri, 24 Apr 2015 12:20:44 -0400 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t3OGKgR6015295 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Fri, 24 Apr 2015 12:20:42 -0400 Date: Fri, 24 Apr 2015 18:20:39 +0200 From: Kashyap Chamarthy Message-ID: <20150424162039.GA25722@tesla.redhat.com> References: <1429864368-15249-1-git-send-email-kchamart@redhat.com> <553A66A0.9020608@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <553A66A0.9020608@redhat.com> Subject: Re: [Qemu-devel] [PATCH v2] qmp-commands.hx: Update the supported 'transaction' operations List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: John Snow Cc: kwolf@redhat.com, qemu-devel@nongnu.org, lcapitulino@redhat.com On Fri, Apr 24, 2015 at 11:52:00AM -0400, John Snow wrote: > > On 04/24/2015 04:32 AM, Kashyap Chamarthy wrote: [. . .] > These: > > > block-dirty-bitmap-add > > block-dirty-bitmap-clear > > > > Aren't merged yet, so it might be a little confusing. Yeah, I expected someone to call that out, that's the reason I added the NB at the end of the commit message which explicitly states that these will be usable once your series (linked below) is merged, hoping that'd clarify. > We could tack this on to the end of the transaction series if you'd > like, and hopefully that all goes in at once before 2.4. That works too. If it's preferable, I can respin this to remove the mention of above two commands and resubmit a v3. -- /kashyap > >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 > > > >Signed-off-by: Kashyap Chamarthy > >Reviewed-by: Eric Blake > >--- > > From v1 -> v2: > > > > - Update the "NB" part of the commit message by removing the duplicate > > command entry and add the missing one ('block-dirty-bitmap-clear') > > - Fix grammer per Eric Blake's review: s/refer/refer to the > >--- > > qmp-commands.hx | 13 ++++++++----- > > 1 file changed, 8 insertions(+), 5 deletions(-) > > > >diff --git a/qmp-commands.hx b/qmp-commands.hx > >index 3a42ad0bffeb23778f877410f6e2038943da46c0..b7fe31ca37afe0f4ae8f4b6f7be5d379b361b1b8 100644 > >--- a/qmp-commands.hx > >+++ b/qmp-commands.hx > >@@ -1200,11 +1200,14 @@ 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 > >