From: Eric Blake <eblake@redhat.com>
To: Peter Krempa <pkrempa@redhat.com>, qemu-devel@nongnu.org
Cc: Igor Mammedov <imammedo@redhat.com>, David Gibson <dgibson@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/2] qapi: keep names in 'CpuInstanceProperties' in sync with struct CPUCore
Date: Thu, 23 Jun 2016 16:03:27 -0600 [thread overview]
Message-ID: <576C5CAF.1030408@redhat.com> (raw)
In-Reply-To: <61d5b28a8a8e540a111e5bb6814d8082f1d69dda.1466716710.git.pkrempa@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2158 bytes --]
On 06/23/2016 03:23 PM, Peter Krempa wrote:
> struct CPUCore uses 'id' suffix in the property name. As docs for
> query-hotpluggable-cpus state that the cpu core properties should be
> passed back to device_add by management in case new members are added
> and thus the names for the fields should be kept in sync.
>
> Signed-off-by: Peter Krempa <pkrempa@redhat.com>
> ---
> hmp.c | 16 ++++++++--------
> hw/ppc/spapr.c | 4 ++--
> include/hw/cpu/core.h | 3 +++
> qapi-schema.json | 19 ++++++++++---------
> 4 files changed, 23 insertions(+), 19 deletions(-)
>
> +++ b/qapi-schema.json
> @@ -4267,20 +4267,21 @@
> # Note: currently there are 4 properties that could be present
> # but management should be prepared to pass through other
> # properties with device_add command to allow for future
> -# interface extension.
> +# interface extension. This also requires the filed names to be kept in sync
> +# sync with the properties passed to -device/device_add.
s/sync sync/sync/
> #
> -# @node: #optional NUMA node ID the CPU belongs to
> -# @socket: #optional socket number within node/board the CPU belongs to
> -# @core: #optional core number within socket the CPU belongs to
> -# @thread: #optional thread number within core the CPU belongs to
> +# @node-id: #optional NUMA node ID the CPU belongs to
> +# @socket-id: #optional socket number within node/board the CPU belongs to
> +# @core-id: #optional core number within socket the CPU belongs to
> +# @thread-id: #optional thread number within core the CPU belongs to
> #
> # Since: 2.7
> ##
> { 'struct': 'CpuInstanceProperties',
> - 'data': { '*node': 'int',
> - '*socket': 'int',
> - '*core': 'int',
> - '*thread': 'int'
> + 'data': { '*node-id': 'int',
> + '*socket-id': 'int',
> + '*core-id': 'int',
> + '*thread-id': 'int'
> }
> }
>
with the duplicate word fixed,
Reviewed-by: Eric Blake <eblake@redhat.com>
--
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-06-23 22:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 21:23 [Qemu-devel] [PATCH v2 0/2] qapi: Fix up cpu hotplug property names and add witness for cpu hotplug support Peter Krempa
2016-06-23 21:23 ` [Qemu-devel] [PATCH v2 1/2] qapi: Report support for -device cpu hotplug in query-machines Peter Krempa
2016-06-24 6:24 ` Igor Mammedov
2016-06-23 21:23 ` [Qemu-devel] [PATCH v2 2/2] qapi: keep names in 'CpuInstanceProperties' in sync with struct CPUCore Peter Krempa
2016-06-23 22:03 ` Eric Blake [this message]
2016-06-24 5:32 ` Igor Mammedov
2016-06-24 3:00 ` [Qemu-devel] [PATCH v2 0/2] qapi: Fix up cpu hotplug property names and add witness for cpu hotplug support David Gibson
2016-06-24 5:31 ` Igor Mammedov
2016-06-24 5:38 ` David Gibson
2016-06-27 3:16 ` David Gibson
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=576C5CAF.1030408@redhat.com \
--to=eblake@redhat.com \
--cc=dgibson@redhat.com \
--cc=imammedo@redhat.com \
--cc=pkrempa@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 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.