qapi: convert "Example" sections with titles

When an Example section has a brief explanation, convert it to a
qmp-example:: section using the :title: option.

Rule of thumb: If the title can fit on a single line and requires no rST
markup, it's a good candidate for using the :title: option of
qmp-example.

In this patch, trailing punctuation is removed from the title section
for consistent headline aesthetics. In just one case, specifics of the
example are removed to make the title read better.

See commit-4: "docs/qapidoc: create qmp-example directive", for a
              detailed explanation of this custom directive syntax.

See commit+2: "qapi: remove "Example" doc section" for a detailed
              explanation of why.

Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Message-ID: <20240717021312.606116-8-jsnow@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
This commit is contained in:
John Snow 2024-07-16 22:13:09 -04:00 committed by Markus Armbruster
parent 14b48aaab9
commit a9eab6e2e6
6 changed files with 52 additions and 48 deletions

View File

@ -5881,9 +5881,8 @@
#
# Since: 2.7
#
# Examples:
#
# 1. Add a new node to a quorum
# .. qmp-example::
# :title: Add a new node to a quorum
#
# -> { "execute": "blockdev-add",
# "arguments": {
@ -5897,7 +5896,8 @@
# "node": "new_node" } }
# <- { "return": {} }
#
# 2. Delete a quorum's node
# .. qmp-example::
# :title: Delete a quorum's node
#
# -> { "execute": "x-blockdev-change",
# "arguments": { "parent": "disk1",
@ -5933,16 +5933,16 @@
#
# Since: 2.12
#
# Examples:
#
# 1. Move a node into an IOThread
# .. qmp-example::
# :title: Move a node into an IOThread
#
# -> { "execute": "x-blockdev-set-iothread",
# "arguments": { "node-name": "disk1",
# "iothread": "iothread0" } }
# <- { "return": {} }
#
# 2. Move a node into the main loop
# .. qmp-example::
# :title: Move a node into the main loop
#
# -> { "execute": "x-blockdev-set-iothread",
# "arguments": { "node-name": "disk1",
@ -6018,16 +6018,16 @@
#
# Since: 2.0
#
# Examples:
#
# 1. Read operation
# .. qmp-example::
# :title: Read operation
#
# <- { "event": "QUORUM_REPORT_BAD",
# "data": { "node-name": "node0", "sector-num": 345435, "sectors-count": 5,
# "type": "read" },
# "timestamp": { "seconds": 1344522075, "microseconds": 745528 } }
#
# 2. Flush operation
# .. qmp-example::
# :title: Flush operation
#
# <- { "event": "QUORUM_REPORT_BAD",
# "data": { "node-name": "node0", "sector-num": 0, "sectors-count": 2097120,

View File

@ -342,9 +342,8 @@
#
# Since: 2.5
#
# Examples:
#
# 1. Change a removable medium
# .. qmp-example::
# :title: Change a removable medium
#
# -> { "execute": "blockdev-change-medium",
# "arguments": { "id": "ide0-1-0",
@ -352,7 +351,8 @@
# "format": "raw" } }
# <- { "return": {} }
#
# 2. Load a read-only medium into a writable drive
# .. qmp-example::
# :title: Load a read-only medium into a writable drive
#
# -> { "execute": "blockdev-change-medium",
# "arguments": { "id": "floppyA",
@ -577,9 +577,8 @@
# "boundaries-write": [1000, 5000] } }
# <- { "return": {} }
#
# Example:
#
# Remove all latency histograms:
# .. qmp-example::
# :title: Remove all latency histograms
#
# -> { "execute": "block-latency-histogram-set",
# "arguments": { "id": "drive0" } }

View File

@ -287,14 +287,14 @@
#
# Since: 0.14
#
# Examples:
#
# 1. Before the first migration
# .. qmp-example::
# :title: Before the first migration
#
# -> { "execute": "query-migrate" }
# <- { "return": {} }
#
# 2. Migration is done and has succeeded
# .. qmp-example::
# :title: Migration is done and has succeeded
#
# -> { "execute": "query-migrate" }
# <- { "return": {
@ -314,12 +314,14 @@
# }
# }
#
# 3. Migration is done and has failed
# .. qmp-example::
# :title: Migration is done and has failed
#
# -> { "execute": "query-migrate" }
# <- { "return": { "status": "failed" } }
#
# 4. Migration is being performed:
# .. qmp-example::
# :title: Migration is being performed
#
# -> { "execute": "query-migrate" }
# <- {
@ -340,7 +342,8 @@
# }
# }
#
# 5. Migration is being performed and XBZRLE is active:
# .. qmp-example::
# :title: Migration is being performed and XBZRLE is active
#
# -> { "execute": "query-migrate" }
# <- {
@ -2131,15 +2134,15 @@
#
# Since: 5.2
#
# Examples:
#
# 1. Measurement is in progress:
# .. qmp-example::
# :title: Measurement is in progress
#
# <- {"status": "measuring", "sample-pages": 512,
# "mode": "page-sampling", "start-time": 1693900454, "calc-time": 10,
# "calc-time-unit": "second"}
#
# 2. Measurement has been completed:
# .. qmp-example::
# :title: Measurement has been completed
#
# <- {"status": "measured", "sample-pages": 512, "dirty-rate": 108,
# "mode": "page-sampling", "start-time": 1693900454, "calc-time": 10,

View File

@ -104,16 +104,16 @@
#
# Since: 1.2
#
# Examples:
#
# 1. Use absolute path
# .. qmp-example::
# :title: Use absolute path
#
# -> { "execute": "qom-get",
# "arguments": { "path": "/machine/unattached/device[0]",
# "property": "hotplugged" } }
# <- { "return": false }
#
# 2. Use partial path
# .. qmp-example::
# :title: Use partial path
#
# -> { "execute": "qom-get",
# "arguments": { "path": "unattached/sysbus",

View File

@ -1270,9 +1270,8 @@
# property, so it is possible to map which console belongs to which
# device and display.
#
# Examples:
#
# 1. Press left mouse button.
# .. qmp-example::
# :title: Press left mouse button
#
# -> { "execute": "input-send-event",
# "arguments": { "device": "video0",
@ -1286,7 +1285,8 @@
# "data" : { "down": false, "button": "left" } } ] } }
# <- { "return": {} }
#
# 2. Press ctrl-alt-del.
# .. qmp-example::
# :title: Press ctrl-alt-del
#
# -> { "execute": "input-send-event",
# "arguments": { "events": [
@ -1298,7 +1298,8 @@
# "key": {"type": "qcode", "data": "delete" } } } ] } }
# <- { "return": {} }
#
# 3. Move mouse pointer to absolute coordinates (20000, 400).
# .. qmp-example::
# :title: Move mouse pointer to absolute coordinates
#
# -> { "execute": "input-send-event" ,
# "arguments": { "events": [

View File

@ -690,9 +690,8 @@
#
# Since: 7.2
#
# Examples:
#
# 1. Get vhost_virtqueue status for vhost-crypto
# .. qmp-example::
# :title: Get vhost_virtqueue status for vhost-crypto
#
# -> { "execute": "x-query-virtio-vhost-queue-status",
# "arguments": { "path": "/machine/peripheral/crypto0/virtio-backend",
@ -715,7 +714,8 @@
# }
# }
#
# 2. Get vhost_virtqueue status for vhost-vsock
# .. qmp-example::
# :title: Get vhost_virtqueue status for vhost-vsock
#
# -> { "execute": "x-query-virtio-vhost-queue-status",
# "arguments": { "path": "/machine/peripheral/vsock0/virtio-backend",
@ -839,9 +839,8 @@
#
# Since: 7.2
#
# Examples:
#
# 1. Introspect on virtio-net's VirtQueue 0 at index 5
# .. qmp-example::
# :title: Introspect on virtio-net's VirtQueue 0 at index 5
#
# -> { "execute": "x-query-virtio-queue-element",
# "arguments": { "path": "/machine/peripheral-anon/device[1]/virtio-backend",
@ -870,7 +869,8 @@
# }
# }
#
# 2. Introspect on virtio-crypto's VirtQueue 1 at head
# .. qmp-example::
# :title: Introspect on virtio-crypto's VirtQueue 1 at head
#
# -> { "execute": "x-query-virtio-queue-element",
# "arguments": { "path": "/machine/peripheral/crypto0/virtio-backend",
@ -898,7 +898,8 @@
# }
# }
#
# 3. Introspect on virtio-scsi's VirtQueue 2 at head
# .. qmp-example::
# :title: Introspect on virtio-scsi's VirtQueue 2 at head
#
# -> { "execute": "x-query-virtio-queue-element",
# "arguments": { "path": "/machine/peripheral-anon/device[2]/virtio-backend",