From: Paolo Bonzini <pbonzini@redhat.com>
To: gaowanlong@cn.fujitsu.com
Cc: andre.przywara@amd.com, aliguori@us.ibm.com,
Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org, Bandan Das <bsd@redhat.com>,
y-goto@jp.fujitsu.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH 3/7] NUMA: parse guest numa nodes memory policy
Date: Wed, 19 Jun 2013 19:39:05 +0200 [thread overview]
Message-ID: <51C1ECB9.6060201@redhat.com> (raw)
In-Reply-To: <51C1653F.4000902@cn.fujitsu.com>
Il 19/06/2013 10:01, Wanlong Gao ha scritto:
> On 06/19/2013 04:19 AM, Bandan Das wrote:
>> Eduardo Habkost <ehabkost@redhat.com> writes:
>>
>>> On Tue, Jun 18, 2013 at 11:20:37AM +0200, Paolo Bonzini wrote:
>>> [...]
>>>> Also, please use QemuOpts instead of yet another homegrown parser.
>>>> Eduardo, I think you had the most recent attempt to convert -numa to
>>>> QemuOpts?
>>>
>>> I had one, but I believe it is more complex than it should have been. I
>>> was creating a "numa-node" config section while keeping "-numa" just for
>>> compatbility, but I don't think we really need to do that.
>>
>> Ah, I was working on an update to Eduardo's earlier proposals for multiple CPU ranges
>> and part of the change was to convert to QemuOpts.
>>
>> Probably needs more testing but posted it anyway since we are already discussing this :
>> [PATCH v3] vl.c: Support multiple CPU ranges on -numa option
>> (hasn't shown up in the archives yet)
>
> Here is the archive: http://thread.gmane.org/gmane.comp.emulators.qemu/217491
>
> So, are you all ACK with this? And we are not considering compatible thing by using
> "cpu" instead of "cpus" here?
No; as Eduardo pointed out, the "cpus" must be kept. But apart from
that, picking up Bandan's patch in v2 of this series should be fine.
Paolo
next prev parent reply other threads:[~2013-06-19 17:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 8:09 [Qemu-devel] [PATCH 0/7] Add support for binding guest numa nodes to host numa nodes Wanlong Gao
2013-06-18 8:09 ` [Qemu-devel] [PATCH 1/7] Add numa_info structure to contain numa nodes info Wanlong Gao
2013-06-18 8:09 ` [Qemu-devel] [PATCH 2/7] Add Linux libnuma detection Wanlong Gao
2013-06-18 8:09 ` [Qemu-devel] [PATCH 3/7] NUMA: parse guest numa nodes memory policy Wanlong Gao
2013-06-18 9:20 ` Paolo Bonzini
2013-06-18 9:54 ` Wanlong Gao
2013-06-18 19:00 ` Eduardo Habkost
2013-06-18 20:19 ` Bandan Das
2013-06-19 8:01 ` Wanlong Gao
2013-06-19 17:39 ` Paolo Bonzini [this message]
2013-06-20 0:01 ` Wanlong Gao
2013-06-18 8:09 ` [Qemu-devel] [PATCH 4/7] NUMA: set " Wanlong Gao
2013-06-18 8:09 ` [Qemu-devel] [PATCH 5/7] NUMA: add qmp command set-mpol to set memory policy for NUMA node Wanlong Gao
2013-06-18 9:21 ` Paolo Bonzini
2013-06-18 9:44 ` Wanlong Gao
2013-06-18 9:57 ` Paolo Bonzini
2013-06-18 8:09 ` [Qemu-devel] [PATCH 6/7] NUMA: add hmp command set-mpol Wanlong Gao
2013-06-18 9:23 ` Paolo Bonzini
2013-06-18 9:49 ` Wanlong Gao
2013-06-18 8:09 ` [Qemu-devel] [PATCH 7/7] NUMA: show host memory policy info in info numa command 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=51C1ECB9.6060201@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=andre.przywara@amd.com \
--cc=bsd@redhat.com \
--cc=ehabkost@redhat.com \
--cc=gaowanlong@cn.fujitsu.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).