From: Eric Blake <eblake@redhat.com>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: ehabkost@redhat.com, aik@ozlabs.ru, armbru@redhat.com,
agraf@suse.de, pbonzini@redhat.com, imammedo@redhat.com,
afaerber@suse.de, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [RFC PATCH v0 7/8] qmp: Implement query cpu-packages
Date: Mon, 22 Feb 2016 09:49:40 -0700 [thread overview]
Message-ID: <56CB3C24.5060001@redhat.com> (raw)
In-Reply-To: <1456117285-22273-8-git-send-email-bharata@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 2077 bytes --]
On 02/21/2016 10:01 PM, Bharata B Rao wrote:
> Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> ---
> hw/cpu/package.c | 19 +++++++++++++
> hw/ppc/spapr.c | 79 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> include/hw/boards.h | 1 +
> qapi-schema.json | 48 ++++++++++++++++++++++++++++++++
> 4 files changed, 147 insertions(+)
>
> +++ b/qapi-schema.json
> @@ -4083,3 +4083,51 @@
> ##
> { 'enum': 'ReplayMode',
> 'data': [ 'none', 'record', 'play' ] }
> +
> +##
> +# @CPUThreadInfo:
> +#
> +# Information about CPU Threads
> +#
Missing documentation for the fields.
> +# Since: 2.6
> +##
> +
> +{ 'struct': 'CPUInfo',
> + 'data': { 'arch_id': 'int',
New QMP code should favor '-' over '_'; this should be 'arch-id'.
> + 'type': 'str',
Is this string free-form, or is it a finite set of values? If the
latter, then it should be an enum type.
> + '*thread': 'int',
> + '*core': 'int',
> + '*socket' : 'int',
> + '*node' : 'int',
> + '*qom_path': 'str'
'qom-path'. But this one is definitely free-form, so 'str' is right.
> + }
> +}
> +
> +##
> +# @CPUPackageInfo:
> +#
> +# Information about CPU Packages
> +#
Missing field documentation.
> +# Since: 2.6
> +##
> +
> +{ 'struct': 'CPUPackageInfo',
> + 'data': { '*id': 'str',
> + 'type': 'str',
> + 'qom_path': 'str',
> + 'realized': 'bool',
> + 'nr_cpus': 'int',
'nr-cpus'. Is this field redundant, given that the caller can just count
the length of the 'cpus' array?
> + 'cpus' : ['CPUInfo']
> + }
> +}
> +
> +##
> +# @query-cpu-packages:
> +#
> +# Returns information for all CPU packages
> +#
> +# Returns: a list of @CPUPackageInfo
> +#
> +# Since: 2.6
> +##
> +{ 'command': 'query-cpu-packages', 'returns': ['CPUPackageInfo'] }
>
--
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: 604 bytes --]
next prev parent reply other threads:[~2016-02-22 16:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 5:01 [Qemu-devel] [RFC PATCH v0 0/8] cpu-package hotplug Bharata B Rao
2016-02-22 5:01 ` [Qemu-devel] [RFC PATCH v0 1/8] cpu: Store CPU typename in MachineState Bharata B Rao
2016-02-22 8:04 ` David Gibson
2016-02-22 5:01 ` [Qemu-devel] [RFC PATCH v0 2/8] cpu: Don't realize CPU from cpu_generic_init() Bharata B Rao
2016-02-22 5:01 ` [Qemu-devel] [RFC PATCH v0 3/8] cpu: CPU package abstract device Bharata B Rao
2016-02-22 5:01 ` [Qemu-devel] [RFC PATCH v0 4/8] spapr: Introduce CPU core device Bharata B Rao
2016-02-22 6:44 ` Andreas Färber
2016-02-22 7:47 ` David Gibson
2016-02-22 15:58 ` Andreas Färber
2016-02-22 23:24 ` David Gibson
2016-02-22 8:05 ` Bharata B Rao
2016-02-22 15:48 ` Andreas Färber
2016-02-22 5:01 ` [Qemu-devel] [RFC PATCH v0 5/8] spapr: Convert boot CPUs into CPU core device initialization Bharata B Rao
2016-02-22 5:01 ` [Qemu-devel] [RFC PATCH v0 6/8] spapr: CPU hotplug support Bharata B Rao
2016-02-22 5:01 ` [Qemu-devel] [RFC PATCH v0 7/8] qmp: Implement query cpu-packages Bharata B Rao
2016-02-22 16:49 ` Eric Blake [this message]
2016-02-23 8:37 ` Igor Mammedov
2016-02-22 5:01 ` [Qemu-devel] [RFC PATCH v0 8/8] hmp: Implement 'info cpu-slots' Bharata B Rao
2016-02-22 5:10 ` [Qemu-devel] [RFC PATCH v0 0/8] cpu-package hotplug Bharata B Rao
2016-02-22 15:32 ` Andreas Färber
2016-02-22 23:28 ` David Gibson
2016-02-23 6:11 ` Bharata B Rao
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=56CB3C24.5060001@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=armbru@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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 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).