qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, benoit.canet@irqsave.net, pkrempa@redhat.com,
	famz@redhat.com, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH v4 09/10] block: Add QMP documentation for block-stream
Date: Wed,  4 Jun 2014 09:51:11 -0400	[thread overview]
Message-ID: <c93d20617072ea88a8934bfdf2951b8d5fa16e95.1401886089.git.jcody@redhat.com> (raw)
In-Reply-To: <cover.1401886089.git.jcody@redhat.com>
In-Reply-To: <cover.1401886089.git.jcody@redhat.com>

The QMP command 'block-stream' was missing QMP documentation.  Add
that documentation.

Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Jeff Cody <jcody@redhat.com>
---
 qmp-commands.hx | 58 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 58 insertions(+)

diff --git a/qmp-commands.hx b/qmp-commands.hx
index b41af0f..69d29ae 100644
--- a/qmp-commands.hx
+++ b/qmp-commands.hx
@@ -983,6 +983,64 @@ EQMP
         .mhandler.cmd_new = qmp_marshal_input_block_stream,
     },
 
+SQMP
+block-stream
+------------
+
+Copy data from a backing file into a block device.
+
+The block streaming operation is performed in the background until the entire
+backing file has been copied.  This command returns immediately once streaming
+has started.  The status of ongoing block streaming operations can be checked
+with query-block-jobs.  The operation can be stopped before it has completed
+using the block-job-cancel command.
+
+If a base file is specified then sectors are not copied from that base file and
+its backing chain.  When streaming completes the image file will have the base
+file as its backing file.  This can be used to stream a subset of the backing
+file chain instead of flattening the entire image.
+
+On successful completion the image file is updated to drop the backing file
+and the BLOCK_JOB_COMPLETED event is emitted.
+
+- "device":         The device name.
+                    (json-string)
+
+For base, either 'base' or 'base-node-name' may be set but not both. If
+neither is specified, the entire chain will be streamed into the active image,
+and the chain will consist of a single image (the current active layer) with
+no backing file.
+
+- "base":           The common backing file name.
+                    (json-string, optional)
+
+- "base-node-name": The block driver state node name of the common backing file.
+                    (json-string, optional) (Since 2.1)
+
+- "backing-file":   The backing file string to write into the active layer.
+                    This filename is not validated.
+
+                    If a pathname string is such that it cannot be resolved by
+                    QEMU, that means that subsequent QMP or HMP commands must
+                    use node-names for the image in question, as filename
+                    lookup methods will fail.
+
+                    If not specified, QEMU will automatically determine the
+                    backing file string to use, or error out if there is no
+                    obvious choice.  Care should be taken when specifying the
+                    string, to specify a valid filename or protocol.
+                    (json-string, optional)
+                    (Since 2.1)
+
+- "speed":          The maximum speed, in bytes per second.
+                    (json-int, optional)
+
+- "on-error":       The action to take on an error (default report).
+                    'stop' and 'enospc' can only be used if the block device
+                    supports io-status (see BlockInfo).
+                    (json-enum, optional) (Since 1.3)
+EQMP
+
     {
         .name       = "block-commit",
         .args_type  = "device:B,base:s?,base-node-name:s?,top:s?,top-node-name:s?,backing-file:s?,speed:o?",
-- 
1.9.3

  parent reply	other threads:[~2014-06-04 13:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 13:51 [Qemu-devel] [PATCH v4 00/10] Modify block jobs to use node-names Jeff Cody
2014-06-04 13:51 ` [Qemu-devel] [PATCH v4 01/10] block: Auto-generate node_names for each BDS entry Jeff Cody
2014-06-04 13:51 ` [Qemu-devel] [PATCH v4 02/10] block: add helper function to determine if a BDS is in a chain Jeff Cody
2014-06-04 13:51 ` [Qemu-devel] [PATCH v4 03/10] block: simplify bdrv_find_base() and bdrv_find_overlay() Jeff Cody
2014-06-04 19:45   ` Eric Blake
2014-06-04 13:51 ` [Qemu-devel] [PATCH v4 04/10] block: make 'top' argument to block-commit optional Jeff Cody
2014-06-04 20:59   ` Eric Blake
2014-06-05  0:26     ` Jeff Cody
2014-06-04 13:51 ` [Qemu-devel] [PATCH v4 05/10] block: Accept node-name arguments for block-commit Jeff Cody
2014-06-04 21:38   ` Eric Blake
2014-06-05  0:57     ` Jeff Cody
2014-06-04 13:51 ` [Qemu-devel] [PATCH v4 06/10] block: extend block-commit to accept a string for the backing file Jeff Cody
2014-06-04 13:51 ` [Qemu-devel] [PATCH v4 07/10] block: add ability for block-stream to use node-name Jeff Cody
2014-06-05  2:22   ` Eric Blake
2014-06-04 13:51 ` [Qemu-devel] [PATCH v4 08/10] block: add backing-file option to block-stream Jeff Cody
2014-06-04 13:51 ` Jeff Cody [this message]
2014-06-04 13:51 ` [Qemu-devel] [PATCH v4 10/10] block: add QAPI command to allow live backing file change Jeff Cody
2014-06-05  2:38   ` Eric Blake
2014-06-05 11:53   ` Benoît Canet

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=c93d20617072ea88a8934bfdf2951b8d5fa16e95.1401886089.git.jcody@redhat.com \
    --to=jcody@redhat.com \
    --cc=benoit.canet@irqsave.net \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pkrempa@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).