From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Victor Toso de Carvalho" <victortoso@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"John Snow" <jsnow@redhat.com>
Subject: [PATCH 26/27] docs/qapi-domain: RFC patch - Add one last sample command
Date: Fri, 19 Apr 2024 00:38:14 -0400 [thread overview]
Message-ID: <20240419043820.178731-27-jsnow@redhat.com> (raw)
In-Reply-To: <20240419043820.178731-1-jsnow@redhat.com>
Just to have a bit more to look at in the generated doc, here's a fairly
complex command with a lot of bells and whistles.
Signed-off-by: John Snow <jsnow@redhat.com>
---
docs/qapi/index.rst | 67 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 67 insertions(+)
diff --git a/docs/qapi/index.rst b/docs/qapi/index.rst
index 6e85ea5280d..4562e755d21 100644
--- a/docs/qapi/index.rst
+++ b/docs/qapi/index.rst
@@ -267,6 +267,73 @@ Explicit cross-referencing syntax for QAPI modules is available with
:memb str key-secret: ID of a QCryptoSecret object providing a
passphrase for unlocking the encryption
+.. qapi:command:: blockdev-backup
+ :since: 4.2
+
+ Start a point-in-time copy of a block device to a new
+ destination. The status of ongoing blockdev-backup operations can be
+ checked with query-block-jobs where the BlockJobInfo.type field has
+ the value ‘backup’. The operation can be stopped before it has
+ completed using the block-job-cancel command.
+
+ :arg str target:
+ the device name or node-name of the backup target node.
+ :arg str? job-id:
+ identifier for the newly-created block job. If omitted, the device
+ name will be used. (Since 2.7)
+ :arg str device:
+ the device name or node-name of a root node which should be copied.
+ :arg MirrorSyncMode sync:
+ what parts of the disk image should be copied to the destination
+ (all the disk, only the sectors allocated in the topmost image,
+ from a dirty bitmap, or only new I/O).
+ :arg int? speed:
+ the maximum speed, in bytes per second. The default is 0, for unlimited.
+ :arg str? bitmap:
+ The name of a dirty bitmap to use. Must be present if sync is
+ ``bitmap`` or ``incremental``. Can be present if sync is ``full`` or
+ ``top``. Must not be present otherwise. (Since 2.4 (drive-backup),
+ 3.1 (blockdev-backup))
+ :arg BitmapSyncMode? bitmap-mode:
+ Specifies the type of data the bitmap should contain after the
+ operation concludes. Must be present if a bitmap was provided,
+ Must NOT be present otherwise. (Since 4.2)
+ :arg bool? compress:
+ true to compress data, if the target format supports it. (default:
+ false) (since 2.8)
+ :arg BlockdevOnError? on-source-error:
+ the action to take on an error on the source, default
+ ``report``. ``stop`` and ``enospc`` can only be used if the block device
+ supports io-status (see BlockInfo).
+ :arg BlockdevOnError? on-target-error:
+ the action to take on an error on the target, default ``report`` (no
+ limitations, since this applies to a different block device than
+ device).
+ :arg bool? auto-finalize:
+ When false, this job will wait in a ``PENDING`` state after it has
+ finished its work, waiting for block-job-finalize before making
+ any block graph changes. When true, this job will automatically
+ perform its abort or commit actions. Defaults to true. (Since
+ 2.12)
+ :arg bool? auto-dismiss:
+ When false, this job will wait in a ``CONCLUDED`` state after it has
+ completely ceased all work, and awaits block-job-dismiss. When
+ true, this job will automatically disappear from the query list
+ without user intervention. Defaults to true. (Since 2.12)
+ :arg str? filter-node-name:
+ the node name that should be assigned to the filter driver that
+ the backup job inserts into the graph above node specified by
+ drive. If this option is not given, a node name is
+ autogenerated. (Since: 4.2)
+ :arg BackupPerf? x-perf:
+ Performance options. (Since 6.0)
+ :feat unstable: Member ``x-perf`` is experimental.
+ :error DeviceNotFound: if ``device`` is not a valid block device.
+
+ .. note:: ``on-source-error`` and ``on-target-error only`` affect
+ background I/O. If an error occurs during a guest write
+ request, the device's rerror/werror actions will be used.
+
.. qapi:command:: x-debug-query-block-graph
:since: 4.0
:unstable:
--
2.44.0
next prev parent reply other threads:[~2024-04-19 4:40 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 4:37 [PATCH 00/27] Add qapi-domain Sphinx extension John Snow
2024-04-19 4:37 ` [PATCH 01/27] docs/sphinx: create QAPI domain extension stub John Snow
2024-04-19 4:37 ` [PATCH 02/27] docs/qapi-domain: add qapi:module directive John Snow
2024-04-19 4:37 ` [PATCH 03/27] docs/qapi-module: add QAPI domain object registry John Snow
2024-04-19 4:37 ` [PATCH 04/27] docs/qapi-domain: add QAPI index John Snow
2024-04-19 4:37 ` [PATCH 05/27] docs/qapi-domain: add resolve_any_xref() John Snow
2024-04-19 4:37 ` [PATCH 06/27] docs/qapi-domain: add QAPI xref roles John Snow
2024-04-19 4:37 ` [PATCH 07/27] docs/qapi-domain: add qapi:command directive John Snow
2024-04-19 4:37 ` [PATCH 08/27] docs/qapi-domain: add :since: directive option John Snow
2024-04-19 4:37 ` [PATCH 09/27] docs/qapi-domain: add "Arguments:" field lists John Snow
2024-04-19 4:37 ` [PATCH 10/27] docs/qapi-domain: add "Features:" " John Snow
2024-04-19 4:37 ` [PATCH 11/27] docs/qapi-domain: add "Errors:" " John Snow
2024-04-19 4:38 ` [PATCH 12/27] docs/qapi-domain: add "Returns:" " John Snow
2024-04-19 4:38 ` [PATCH 13/27] docs/qapi-domain: add qapi:enum directive John Snow
2024-04-19 4:38 ` [PATCH 14/27] docs/qapi-domain: add qapi:alternate directive John Snow
2024-04-19 4:38 ` [PATCH 15/27] docs/qapi-domain: add qapi:event directive John Snow
2024-04-19 4:38 ` [PATCH 16/27] docs/qapi-domain: add qapi:struct directive John Snow
2024-04-19 4:38 ` [PATCH 17/27] docs/qapi-domain: add qapi:union and qapi:branch directives John Snow
2024-04-19 4:38 ` [PATCH 18/27] docs/qapi-domain: add :deprecated: directive option John Snow
2024-04-19 4:38 ` [PATCH 19/27] docs/qapi-domain: add :unstable: " John Snow
2024-04-19 4:38 ` [PATCH 20/27] docs/qapi-domain: add :ifcond: " John Snow
2024-04-19 4:38 ` [PATCH 21/27] docs/qapi-domain: RFC patch - add malformed field list entries John Snow
2024-04-19 4:38 ` [PATCH 22/27] docs/qapi-domain: add warnings for malformed field lists John Snow
2024-04-19 4:38 ` [PATCH 23/27] docs/qapi-domain: RFC patch - delete " John Snow
2024-04-19 4:38 ` [PATCH 24/27] docs/qapi-domain: add type cross-refs to " John Snow
2024-04-19 16:58 ` John Snow
2024-04-19 4:38 ` [PATCH 25/27] docs/qapi-domain: implement error context reporting fix John Snow
2024-04-19 4:38 ` John Snow [this message]
2024-04-19 4:38 ` [PATCH 27/27] docs/qapi-domain: add CSS styling John Snow
2024-04-19 14:45 ` [PATCH 00/27] Add qapi-domain Sphinx extension Markus Armbruster
2024-04-19 15:10 ` Markus Armbruster
2024-04-19 16:31 ` John Snow
2024-04-22 9:19 ` Markus Armbruster
2024-04-22 16:38 ` John Snow
2024-04-23 1:56 ` John Snow
2024-04-23 7:48 ` Markus Armbruster
2024-04-23 18:32 ` John Snow
2024-04-24 14:13 ` Markus Armbruster
2024-04-23 7:19 ` Markus Armbruster
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=20240419043820.178731-27-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=victortoso@redhat.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).