diff --git a/qapi-add-BitmapSyncMode-enum.patch b/qapi-add-BitmapSyncMode-enum.patch new file mode 100644 index 0000000..778faee --- /dev/null +++ b/qapi-add-BitmapSyncMode-enum.patch @@ -0,0 +1,54 @@ +From bd1d5d79f4629520d0753676cea8129c60fc6bbc Mon Sep 17 00:00:00 2001 +From: John Snow +Date: Mon, 29 Jul 2019 16:35:52 -0400 +Subject: [PATCH] qapi: add BitmapSyncMode enum + +Depending on what a user is trying to accomplish, there might be a few +bitmap cleanup actions that occur when an operation is finished that +could be useful. + +I am proposing three: +- NEVER: The bitmap is never synchronized against what was copied. +- ALWAYS: The bitmap is always synchronized, even on failures. +- ON-SUCCESS: The bitmap is synchronized only on success. + +The existing incremental backup modes use 'on-success' semantics, +so add just that one for right now. + +Signed-off-by: John Snow +Reviewed-by: Max Reitz +Reviewed-by: Markus Armbruster +Message-id: 20190709232550.10724-5-jsnow@redhat.com +Signed-off-by: John Snow +--- + qapi/block-core.json | 14 ++++++++++++++ + 1 file changed, 14 insertions(+) + +diff --git a/qapi/block-core.json b/qapi/block-core.json +index 37aa1b7b9a..b8d12a4951 100644 +--- a/qapi/block-core.json ++++ b/qapi/block-core.json +@@ -1134,6 +1134,20 @@ + { 'enum': 'MirrorSyncMode', + 'data': ['top', 'full', 'none', 'incremental'] } + ++## ++# @BitmapSyncMode: ++# ++# An enumeration of possible behaviors for the synchronization of a bitmap ++# when used for data copy operations. ++# ++# @on-success: The bitmap is only synced when the operation is successful. ++# This is the behavior always used for 'INCREMENTAL' backups. ++# ++# Since: 4.2 ++## ++{ 'enum': 'BitmapSyncMode', ++ 'data': ['on-success'] } ++ + ## + # @MirrorCopyMode: + # +-- +2.27.0 +