From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: Igor Mammedov <imammedo@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 2/9] ACPI/unit-test: Add a new testcase for RAM allocation in numa node
Date: Wed, 29 Nov 2017 09:06:56 +0800 [thread overview]
Message-ID: <3e9cab89-519f-dc8e-b371-cb0cb1514eac@cn.fujitsu.com> (raw)
In-Reply-To: <20171128160817.1cb9a9b1@redhat.com>
Hi Igor,
At 11/28/2017 11:08 PM, Igor Mammedov wrote:
> On Thu, 5 Oct 2017 17:36:31 -0300
> Eduardo Habkost <ehabkost@redhat.com> wrote:
>
>> From: Dou Liyang <douly.fnst@cn.fujitsu.com>
>>
>> As QEMU supports the memory-less node, it is possible that there is
>> no RAM in the first numa node(also be called as node0). eg:
>> ... \
>> -m 128,slots=3,maxmem=1G \
>> -numa node -numa node,mem=128M \
>>
>> But, this makes it hard for QEMU to build a known-to-work ACPI SRAT
>> table. Only fixing it is not enough.
>>
>> Add a testcase for this situation to make sure the ACPI table is
>> correct for guest.
>>
>> Suggested-by: Eduardo Habkost <ehabkost@redhat.com>
>> Signed-off-by: Dou Liyang <douly.fnst@cn.fujitsu.com>
>> Message-Id: <1504231805-30957-4-git-send-email-douly.fnst@cn.fujitsu.com>
>> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
>
> Pls retest/respin once dev window is open.
>
Yes, Thanks so much for your reminder. I will do that.
Thanks,
dou.
>
>
>
next prev parent reply other threads:[~2017-11-29 1:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 20:36 [Qemu-devel] [PULL 0/9] x86 and machine queue, 2017-10-05 Eduardo Habkost
2017-10-05 20:36 ` [Qemu-devel] [PULL 1/9] hw/acpi-build: Make assignment statement of next_base easy to read Eduardo Habkost
2017-11-28 15:07 ` Igor Mammedov
2017-11-29 1:07 ` Dou Liyang
2017-10-05 20:36 ` [Qemu-devel] [PULL 2/9] ACPI/unit-test: Add a new testcase for RAM allocation in numa node Eduardo Habkost
2017-11-28 15:08 ` Igor Mammedov
2017-11-29 1:06 ` Dou Liyang [this message]
2017-10-05 20:36 ` [Qemu-devel] [PULL 3/9] qom/cpu: move cpu_model null check to cpu_class_by_name() Eduardo Habkost
2017-10-05 20:36 ` [Qemu-devel] [PULL 4/9] machine: Add a valid_cpu_types property Eduardo Habkost
2017-10-05 20:36 ` [Qemu-devel] [PULL 5/9] vl: Eliminate defconfig variable Eduardo Habkost
2017-10-05 20:36 ` [Qemu-devel] [PULL 6/9] qemu-options: Deprecate -nodefconfig Eduardo Habkost
2017-10-05 20:36 ` [Qemu-devel] [PULL 7/9] config: qemu_config_parse() return number of config groups Eduardo Habkost
2017-10-05 20:36 ` [Qemu-devel] [PULL 8/9] qom: update doc comment for type_register[_static]() Eduardo Habkost
2017-10-05 20:36 ` [Qemu-devel] [PULL 9/9] x86: Correct translation of some rdgsbase and wrgsbase encodings Eduardo Habkost
2017-10-06 12:17 ` [Qemu-devel] [PULL 0/9] x86 and machine queue, 2017-10-05 Peter Maydell
2017-10-06 13:45 ` Thomas Huth
2017-10-06 15:27 ` Eduardo Habkost
2017-10-06 15:37 ` Peter Maydell
2017-10-10 7:41 ` Dou Liyang
2017-10-10 9:40 ` Peter Maydell
2017-10-10 13:29 ` Dou Liyang
2017-10-10 12:52 ` Eduardo Habkost
2017-10-10 12:56 ` Peter Maydell
2017-10-10 14:17 ` Dou Liyang
2017-10-10 16:03 ` Eduardo Habkost
2017-10-10 13:07 ` Dou Liyang
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=3e9cab89-519f-dc8e-b371-cb0cb1514eac@cn.fujitsu.com \
--to=douly.fnst@cn.fujitsu.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=peter.maydell@linaro.org \
--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).