From: "Benoît Canet" <benoit.canet@irqsave.net>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-trivial] [PATCHv2] qmp: fix integer usage in examples
Date: Fri, 30 Aug 2013 23:47:05 +0200 [thread overview]
Message-ID: <20130830214705.GE5170@irqsave.net> (raw)
In-Reply-To: <1377895451-6603-1-git-send-email-eblake@redhat.com>
Le Friday 30 Aug 2013 à 14:44:11 (-0600), Eric Blake a écrit :
> Per the qapi schema, block_set_io_throttle takes most arguments
> as ints, not strings.
>
> * qmp-commands.hx (block_set_io_throttle): Use correct type. Fix
> whitespace and a copy-paste bug in the process.
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
>
> v2: also touch up the doc comments
>
> qmp-commands.hx | 26 +++++++++++++-------------
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/qmp-commands.hx b/qmp-commands.hx
> index bb09e72..8a8f342 100644
> --- a/qmp-commands.hx
> +++ b/qmp-commands.hx
> @@ -1402,22 +1402,22 @@ Change I/O throttle limits for a block drive.
> Arguments:
>
> - "device": device name (json-string)
> -- "bps": total throughput limit in bytes per second(json-int)
> -- "bps_rd": read throughput limit in bytes per second(json-int)
> -- "bps_wr": read throughput limit in bytes per second(json-int)
> -- "iops": total I/O operations per second(json-int)
> -- "iops_rd": read I/O operations per second(json-int)
> -- "iops_wr": write I/O operations per second(json-int)
> +- "bps": total throughput limit in bytes per second (json-int)
> +- "bps_rd": read throughput limit in bytes per second (json-int)
> +- "bps_wr": write throughput limit in bytes per second (json-int)
> +- "iops": total I/O operations per second (json-int)
> +- "iops_rd": read I/O operations per second (json-int)
> +- "iops_wr": write I/O operations per second (json-int)
>
> Example:
>
> -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
> - "bps": "1000000",
> - "bps_rd": "0",
> - "bps_wr": "0",
> - "iops": "0",
> - "iops_rd": "0",
> - "iops_wr": "0" } }
> + "bps": 1000000,
> + "bps_rd": 0,
> + "bps_wr": 0,
> + "iops": 0,
> + "iops_rd": 0,
> + "iops_wr": 0 } }
> <- { "return": {} }
>
> EQMP
> @@ -1791,7 +1791,7 @@ Each json-object contain the following:
> - "vm-state-size": size of the VM state in bytes (json-int)
> - "date-sec": UTC date of the snapshot in seconds (json-int)
> - "date-nsec": fractional part in nanoseconds to be used with
> - date-sec(json-int)
> + date-sec (json-int)
> - "vm-clock-sec": VM clock relative to boot in seconds
> (json-int)
> - "vm-clock-nsec": fractional part in nanoseconds to be used
> --
> 1.8.3.1
>
Reviewed-by: Benoit Canet <benoit@irqsave.net>
WARNING: multiple messages have this Message-ID (diff)
From: "Benoît Canet" <benoit.canet@irqsave.net>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCHv2] qmp: fix integer usage in examples
Date: Fri, 30 Aug 2013 23:47:05 +0200 [thread overview]
Message-ID: <20130830214705.GE5170@irqsave.net> (raw)
In-Reply-To: <1377895451-6603-1-git-send-email-eblake@redhat.com>
Le Friday 30 Aug 2013 à 14:44:11 (-0600), Eric Blake a écrit :
> Per the qapi schema, block_set_io_throttle takes most arguments
> as ints, not strings.
>
> * qmp-commands.hx (block_set_io_throttle): Use correct type. Fix
> whitespace and a copy-paste bug in the process.
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
>
> v2: also touch up the doc comments
>
> qmp-commands.hx | 26 +++++++++++++-------------
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/qmp-commands.hx b/qmp-commands.hx
> index bb09e72..8a8f342 100644
> --- a/qmp-commands.hx
> +++ b/qmp-commands.hx
> @@ -1402,22 +1402,22 @@ Change I/O throttle limits for a block drive.
> Arguments:
>
> - "device": device name (json-string)
> -- "bps": total throughput limit in bytes per second(json-int)
> -- "bps_rd": read throughput limit in bytes per second(json-int)
> -- "bps_wr": read throughput limit in bytes per second(json-int)
> -- "iops": total I/O operations per second(json-int)
> -- "iops_rd": read I/O operations per second(json-int)
> -- "iops_wr": write I/O operations per second(json-int)
> +- "bps": total throughput limit in bytes per second (json-int)
> +- "bps_rd": read throughput limit in bytes per second (json-int)
> +- "bps_wr": write throughput limit in bytes per second (json-int)
> +- "iops": total I/O operations per second (json-int)
> +- "iops_rd": read I/O operations per second (json-int)
> +- "iops_wr": write I/O operations per second (json-int)
>
> Example:
>
> -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
> - "bps": "1000000",
> - "bps_rd": "0",
> - "bps_wr": "0",
> - "iops": "0",
> - "iops_rd": "0",
> - "iops_wr": "0" } }
> + "bps": 1000000,
> + "bps_rd": 0,
> + "bps_wr": 0,
> + "iops": 0,
> + "iops_rd": 0,
> + "iops_wr": 0 } }
> <- { "return": {} }
>
> EQMP
> @@ -1791,7 +1791,7 @@ Each json-object contain the following:
> - "vm-state-size": size of the VM state in bytes (json-int)
> - "date-sec": UTC date of the snapshot in seconds (json-int)
> - "date-nsec": fractional part in nanoseconds to be used with
> - date-sec(json-int)
> + date-sec (json-int)
> - "vm-clock-sec": VM clock relative to boot in seconds
> (json-int)
> - "vm-clock-nsec": fractional part in nanoseconds to be used
> --
> 1.8.3.1
>
Reviewed-by: Benoit Canet <benoit@irqsave.net>
next prev parent reply other threads:[~2013-08-31 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 20:44 [Qemu-trivial] [PATCHv2] qmp: fix integer usage in examples Eric Blake
2013-08-30 20:44 ` [Qemu-devel] " Eric Blake
2013-08-30 21:47 ` Benoît Canet [this message]
2013-08-30 21:47 ` Benoît Canet
2013-09-01 15:47 ` [Qemu-trivial] " Michael Tokarev
2013-09-01 15:47 ` [Qemu-devel] " Michael Tokarev
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=20130830214705.GE5170@irqsave.net \
--to=benoit.canet@irqsave.net \
--cc=eblake@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.