diff options
| -rw-r--r-- | docs/qmp-commands.txt | 18 | ||||
| -rw-r--r-- | qapi/block-core.json | 9 |
2 files changed, 8 insertions, 19 deletions
diff --git a/docs/qmp-commands.txt b/docs/qmp-commands.txt index 6b210d0525..56e47a10e0 100644 --- a/docs/qmp-commands.txt +++ b/docs/qmp-commands.txt @@ -208,24 +208,6 @@ Example: "base": "/tmp/master.qcow2" } } <- { "return": {} } -block-dirty-bitmap-add ----------------------- -Since 2.4 - -Create a dirty bitmap with a name on the device, and start tracking the writes. - -Arguments: - -- "node": device/node on which to create dirty bitmap (json-string) -- "name": name of the new dirty bitmap (json-string) -- "granularity": granularity to track writes with (int, optional) - -Example: - --> { "execute": "block-dirty-bitmap-add", "arguments": { "node": "drive0", - "name": "bitmap0" } } -<- { "return": {} } - block-dirty-bitmap-remove ------------------------- Since 2.4 diff --git a/qapi/block-core.json b/qapi/block-core.json index 546cb8952b..5e97b0b2c8 100644 --- a/qapi/block-core.json +++ b/qapi/block-core.json @@ -1567,13 +1567,20 @@ ## # @block-dirty-bitmap-add: # -# Create a dirty bitmap with a name on the node +# Create a dirty bitmap with a name on the node, and start tracking the writes. # # Returns: nothing on success # If @node is not a valid block device or node, DeviceNotFound # If @name is already taken, GenericError with an explanation # # Since: 2.4 +# +# Example: +# +# -> { "execute": "block-dirty-bitmap-add", +# "arguments": { "node": "drive0", "name": "bitmap0" } } +# <- { "return": {} } +# ## { 'command': 'block-dirty-bitmap-add', 'data': 'BlockDirtyBitmapAdd' } |