qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [PATCH v4 17/17] qmp-commands.txt: fix some styling


From: marcandre . lureau
Subject: [Qemu-devel] [PATCH v4 17/17] qmp-commands.txt: fix some styling
Date: Wed, 10 Aug 2016 22:02:35 +0400

From: Marc-André Lureau <address@hidden>

Add some missing lines, remove superflous @ in command name, remove
trailing spaces.

Signed-off-by: Marc-André Lureau <address@hidden>
---
 docs/qmp-commands.txt | 31 ++++++++++++++++++-------------
 1 file changed, 18 insertions(+), 13 deletions(-)

diff --git a/docs/qmp-commands.txt b/docs/qmp-commands.txt
index dfa1cc1..abd6969 100644
--- a/docs/qmp-commands.txt
+++ b/docs/qmp-commands.txt
@@ -70,7 +70,7 @@ eject
 
 Eject a removable medium.
 
-Arguments: 
+Arguments:
 
 - force: force ejection (json-bool, optional)
 - device: device name (json-string)
@@ -1562,7 +1562,7 @@ human-monitor-command
 
 Execute a Human Monitor command.
 
-Arguments: 
+Arguments:
 
 - command-line: the command name and its arguments, just like the
                 Human Monitor's shell (json-string)
@@ -2288,7 +2288,7 @@ Example:
                   },
                   "function":0,
                   "regions":[
-   
+
                   ]
                },
                {
@@ -2305,7 +2305,7 @@ Example:
                   },
                   "function":0,
                   "regions":[
-   
+
                   ]
                },
                {
@@ -2689,8 +2689,8 @@ The main json-object contains the following:
 - "setup-time" amount of setup time in milliseconds _before_ the
                iterations begin but _after_ the QMP command is issued.
                This is designed to provide an accounting of any activities
-               (such as RDMA pinning) which may be expensive, but do not 
-               actually occur during the iterative migration rounds 
+               (such as RDMA pinning) which may be expensive, but do not
+               actually occur during the iterative migration rounds
                themselves. (json-int)
 - "downtime": only present when migration has finished correctly
               total amount in ms for downtime that happened (json-int)
@@ -3381,8 +3381,8 @@ Delete a quorum's node
                     "child": "children.1" } }
 <- { "return": {} }
 
address@hidden
-------------------------
+query-named-block-nodes
+-----------------------
 
 Return a list of BlockDeviceInfo for all the named block driver nodes
 
@@ -3507,7 +3507,7 @@ Example (1):
      ]
    }
 
address@hidden
+query-memory-devices
 --------------------
 
 Return a list of memory devices.
@@ -3525,8 +3525,9 @@ Example:
                         "slot": 0},
                    "type": "dimm"
                  } ] }
address@hidden
---------------------
+
+query-acpi-ospm-status
+----------------------
 
 Return list of ACPIOSTInfo for devices that support status reporting
 via ACPI _OST method.
@@ -3538,6 +3539,7 @@ Example:
                  { "slot": "2", "slot-type": "DIMM", "source": 0, "status": 0},
                  { "slot": "3", "slot-type": "DIMM", "source": 0, "status": 0}
    ]}
+
 rtc-reset-reinjection
 ---------------------
 
@@ -3549,6 +3551,7 @@ Example:
 
 -> { "execute": "rtc-reset-reinjection" }
 <- { "return": {} }
+
 trace-event-get-state
 ---------------------
 
@@ -3572,6 +3575,7 @@ Example:
 
 -> { "execute": "trace-event-get-state", "arguments": { "name": 
"qemu_memalign" } }
 <- { "return": [ { "name": "qemu_memalign", "state": "disabled" } ] }
+
 trace-event-set-state
 ---------------------
 
@@ -3598,8 +3602,9 @@ Example:
 
 -> { "execute": "trace-event-set-state", "arguments": { "name": 
"qemu_memalign", "enable": "true" } }
 <- { "return": {} }
address@hidden
------------------
+
+input-send-event
+----------------
 
 Send input event to guest.
 
-- 
2.9.0




reply via email to

[Prev in Thread] Current Thread [Next in Thread]