From: Eric Blake <eblake@redhat.com>
To: Sanidhya Kashyap <sanidhya.iiith@gmail.com>,
qemu list <qemu-devel@nongnu.org>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC v2 03/12] VMState test: query command to extract the qdevified device names
Date: Mon, 28 Jul 2014 15:47:15 -0600 [thread overview]
Message-ID: <53D6C4E3.1010701@redhat.com> (raw)
In-Reply-To: <1406302776-2306-4-git-send-email-sanidhya.iiith@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2645 bytes --]
On 07/25/2014 09:39 AM, Sanidhya Kashyap wrote:
> I have provided a qmp interface for getting the list of qdevified devices
> that have been registered with SaveVMHandlers.
>
> Signed-off-by: Sanidhya Kashyap <sanidhya.iiith@gmail.com>
> ---
> qapi-schema.json | 22 ++++++++++++++++++++++
> qmp-commands.hx | 25 +++++++++++++++++++++++++
> savevm.c | 34 ++++++++++++++++++++++++++++++++++
> 3 files changed, 81 insertions(+)
>
> +# @device: list of qdevified device names
> +#
> +# Since 2.2
> +##
> +{ 'type': 'VMStatesQdevDevices',
> + 'data': { 'device': ['str'] } }
Here, you name it 'device' [1]
> +
> +##
> +# @query-qdev-devices
> +#
> +# returns the VMStatesQdevDevices that have the associated value
> +#
> +# Since 2.2
> +##
> +{ 'command': 'query-qdev-devices',
> + 'returns': 'VMStatesQdevDevices' }
and state that it returns a single struct [2]
> diff --git a/qmp-commands.hx b/qmp-commands.hx
> index 4be4765..2e20032 100644
> --- a/qmp-commands.hx
> +++ b/qmp-commands.hx
> @@ -3755,3 +3755,28 @@ Example:
> <- { "return": {} }
>
> EQMP
> +
> + {
> + .name = "query-qdev-devices",
> + .args_type = "",
> + .mhandler.cmd_new = qmp_marshal_input_query_qdev_devices,
> + },
> +
> +SQMP
> +query-qdev-devices
> +------------------
> +
> +Shows registered Qdevified devices
> +
> +
> +Example (1):
> +
> +-> { "execute": "query-qdev-devices" }
> +<- { "return": [
But here, your example shows it returning an array of structs [2]
> + {
> + "devices": [ "kvm-tpr-opt", "piix4_pm" ]
where each struct contains a member named 'devices' [1] that is also an
array.
I actually think the most extensible thing would be to return something
more like this QMP wire contents:
{ "return": [
{ "device": "kvm-tpr-opt" },
{ "device": "piix4_pm" }
] }
which would match this .json content:
{ 'type': 'VMStatesQdevDevices',
'data': { 'device': 'str' } }
{ 'command': 'query-qdev-devices',
'returns': [ 'VMStatesQdevDevices' ] }
and also be the most extensible for future tweaks, such as adding an
optional boolean flag to the json to tell us more about certain devices:
{ 'type': 'VMStatesQdevDevices',
'data': { 'device': 'str', '*foo': 'bool' } }
and lead to this QMP wire transaction:
{ "return": [
{ "device": "kvm-tpr-opt" },
{ "device": "piix4_pm", 'foo': true }
] }
At any rate, you MUST make your example match your documentation.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
next prev parent reply other threads:[~2014-07-28 21:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 15:39 [Qemu-devel] [PATCH RFC v2 00/12] VMState testing Sanidhya Kashyap
2014-07-25 15:39 ` [Qemu-devel] [PATCH RFC v2 01/12] QEMUSizedBuffer/QEMUFile Sanidhya Kashyap
2014-07-28 21:32 ` Eric Blake
2014-08-06 11:11 ` Dr. David Alan Gilbert
2014-07-25 15:39 ` [Qemu-devel] [PATCH RFC v2 02/12] reset handler for qdevified devices Sanidhya Kashyap
2014-07-29 12:43 ` Juan Quintela
2014-07-25 15:39 ` [Qemu-devel] [PATCH RFC v2 03/12] VMState test: query command to extract the qdevified device names Sanidhya Kashyap
2014-07-28 21:47 ` Eric Blake [this message]
2014-07-29 12:45 ` Juan Quintela
2014-07-29 15:14 ` Eric Blake
2014-07-29 17:37 ` Sanidhya Kashyap
2014-07-25 15:39 ` [Qemu-devel] [PATCH RFC v2 04/12] VMState test: hmp interface for showing qdevified devices Sanidhya Kashyap
2014-07-25 15:39 ` [Qemu-devel] [PATCH RFC v2 05/12] VMstate test: basic VMState testing mechanism Sanidhya Kashyap
2014-07-28 21:52 ` Eric Blake
2014-07-29 13:40 ` Juan Quintela
2014-07-29 17:59 ` Sanidhya Kashyap
2014-07-25 15:39 ` [Qemu-devel] [PATCH RFC v2 06/12] VMState test: hmp interface for vmstate testing Sanidhya Kashyap
2014-07-25 15:39 ` [Qemu-devel] [PATCH RFC v2 07/12] VMState test: qmp interface for querying the vmstate testing process Sanidhya Kashyap
2014-07-29 15:17 ` Eric Blake
2014-07-29 16:40 ` Eric Blake
2014-07-25 15:39 ` [Qemu-devel] [PATCH RFC v2 08/12] VMState test: hmp " Sanidhya Kashyap
2014-07-25 15:39 ` [Qemu-devel] [PATCH RFC v2 09/12] VMState test: update period of " Sanidhya Kashyap
2014-07-29 16:48 ` Eric Blake
2014-07-29 18:04 ` Sanidhya Kashyap
2014-07-29 19:42 ` Eric Blake
2014-07-25 15:39 ` [Qemu-devel] [PATCH RFC v2 10/12] VMState test: hmp interface for period update Sanidhya Kashyap
2014-07-25 15:39 ` [Qemu-devel] [PATCH RFC v2 11/12] VMState test: cancel mechanism for an already running vmstate testing process Sanidhya Kashyap
2014-07-29 16:50 ` Eric Blake
2014-07-25 15:39 ` [Qemu-devel] [PATCH RFC v2 12/12] VMState test: hmp interface for cancel mechanism Sanidhya Kashyap
2014-07-29 16:52 ` Eric Blake
2014-07-29 18:06 ` Sanidhya Kashyap
2014-07-30 5:48 ` 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=53D6C4E3.1010701@redhat.com \
--to=eblake@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=sanidhya.iiith@gmail.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).