From: Eric Blake <eblake@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: aliguori@us.ibm.com, ehabkost@redhat.com, qemu-devel@nongnu.org,
peter.huangpeng@huawei.com, lcapitulino@redhat.com,
bsd@redhat.com, y-goto@jp.fujitsu.com, pbonzini@redhat.com,
afaerber@suse.de, Wanlong Gao <gaowanlong@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH V5 01/12] NUMA: add NumaOptions, NumaNodeOptions and NumaMemOptions
Date: Wed, 17 Jul 2013 06:24:47 -0600 [thread overview]
Message-ID: <51E68D0F.4040503@redhat.com> (raw)
In-Reply-To: <51E67368.3000003@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
On 07/17/2013 04:35 AM, Laszlo Ersek wrote:
>> +# @cpus: #optional VCPUs belong to this node
>> +#
>> +# Since: 1.6
>> +##
>> +{ 'type': 'NumaNodeOptions',
>> + 'data': {
>> + '*nodeid': 'int',
>> + '*cpus': 'str' }}
>> +
>
> Should we document the format for "cpus" here too?
Not only that, but is this even the right representation? The fact that
you are requiring the receiver to further parse this string means you
probably represented it at the wrong level in JSON. That is, a JSON
string "1,2,4" requires post-processing to turn it into 3 processor ids,
while a JSON array [1, 2, 4] does not, so you should probably consider
'*cpus':['int'] as your preferred datatype.
>> +# Since 1.6
>> +##
>> +{ 'type': 'NumaMemOptions',
>> + 'data': {
>> + '*nodeid': 'int',
>> + '*size': 'size' }}
>>
>
> Looks good in general but I'm not sure if hardware tabs are allowed (or
> usual) in this file.
Drop the tabs. Also, this missed soft freeze for 1.6, so you will
probably end up using Since 1.7 by the time it actually gets accepted.
--
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: 621 bytes --]
next prev parent reply other threads:[~2013-07-17 12:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 9:29 [Qemu-devel] [PATCH V5 00/12] Add support for binding guest numa nodes to host numa nodes Wanlong Gao
2013-07-17 9:29 ` [Qemu-devel] [PATCH V5 01/12] NUMA: add NumaOptions, NumaNodeOptions and NumaMemOptions Wanlong Gao
2013-07-17 10:35 ` Laszlo Ersek
2013-07-17 11:11 ` Paolo Bonzini
2013-07-17 13:16 ` Wanlong Gao
2013-07-17 12:24 ` Eric Blake [this message]
2013-07-17 13:57 ` Laszlo Ersek
2013-07-17 14:20 ` Paolo Bonzini
2013-07-17 14:33 ` Laszlo Ersek
2013-07-17 14:44 ` Paolo Bonzini
2013-07-17 15:24 ` Laszlo Ersek
2013-07-17 15:26 ` Paolo Bonzini
2013-07-17 15:45 ` Laszlo Ersek
2013-07-17 15:54 ` Paolo Bonzini
2013-07-17 9:29 ` [Qemu-devel] [PATCH V5 02/12] NUMA: split -numa option Wanlong Gao
2013-07-17 11:00 ` Laszlo Ersek
2013-07-17 11:14 ` Paolo Bonzini
2013-07-17 11:13 ` Paolo Bonzini
2013-07-17 9:29 ` [Qemu-devel] [PATCH V5 03/12] NUMA: move numa related code to numa.c Wanlong Gao
2013-07-17 9:29 ` [Qemu-devel] [PATCH V5 04/12] NUMA: Add numa_info structure to contain numa nodes info Wanlong Gao
2013-07-17 9:29 ` [Qemu-devel] [PATCH V5 05/12] NUMA: Add Linux libnuma detection Wanlong Gao
2013-07-17 9:29 ` [Qemu-devel] [PATCH V5 06/12] NUMA: parse guest numa nodes memory policy Wanlong Gao
2013-07-17 12:31 ` Eric Blake
2013-07-17 13:12 ` Wanlong Gao
2013-07-17 9:29 ` [Qemu-devel] [PATCH V5 07/12] NUMA: split out the common range parser Wanlong Gao
2013-07-17 9:29 ` [Qemu-devel] [PATCH V5 08/12] NUMA: set guest numa nodes memory policy Wanlong Gao
2013-07-17 9:29 ` [Qemu-devel] [PATCH V5 09/12] NUMA: add qmp command set-mem-policy to set memory policy for NUMA node Wanlong Gao
2013-07-17 12:36 ` Eric Blake
2013-07-17 13:22 ` Wanlong Gao
2013-07-17 9:29 ` [Qemu-devel] [PATCH V5 10/12] NUMA: add hmp command set-mem-policy Wanlong Gao
2013-07-17 9:29 ` [Qemu-devel] [PATCH V5 11/12] NUMA: add qmp command query-numa Wanlong Gao
2013-07-17 12:41 ` Eric Blake
2013-07-17 13:24 ` Wanlong Gao
2013-07-17 9:29 ` [Qemu-devel] [PATCH V5 12/12] NUMA: convert hmp command info_numa to use qmp command query_numa Wanlong Gao
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=51E68D0F.4040503@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=bsd@redhat.com \
--cc=ehabkost@redhat.com \
--cc=gaowanlong@cn.fujitsu.com \
--cc=lcapitulino@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=y-goto@jp.fujitsu.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).