From: Tang Chen <tangchen@cn.fujitsu.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>,
Igor Mammedov <imammedo@redhat.com>
Cc: Peter <pkrempa@redhat.com>,
mst@redhat.com, Hu Tao <hutao@cn.fujitsu.com>,
luonengjun@huawei.com, peter.huangpeng@huawei.com,
qemu-devel@nongnu.org, pbonzini@redhat.com,
gaowanlong@cn.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH 1/2] pc-dimm: No numa option shouldn't break hotplug memory feature
Date: Tue, 23 Sep 2014 18:32:08 +0800 [thread overview]
Message-ID: <54214C28.4080109@cn.fujitsu.com> (raw)
In-Reply-To: <54214757.7080806@huawei.com>
On 09/23/2014 06:11 PM, zhanghailiang wrote:
> On 2014/9/23 16:58, Tang Chen wrote:
>>
>> On 09/23/2014 04:40 PM, Igor Mammedov wrote:
>>> ......
>>> It's fine to use SRAT for these purposes on baremetal NUMA systems
>>> since
>>> due to used chipset constrains it's possible statically allocate ranges
>>> for every possible DIMM socket.
>>> However SRAT(which is optional table BTW) entries are not mandatory
>>> and override-able by ACPI Device's _PXM/_CRS methods replacing needs
>>> for SRAT entries and QEMU uses this fact by supplying these methods.
>>> QEMU adds FAKE SRAT entry only to workaround Windows limitation,
>>> and for nothing else.
>>>
>>> I think Linux does not violate ACPI spec and behaves as expected,
>>> moreover
>>> it's more correct than Windows since memory hotplug will work on non
>>> NUMA
>>> machines as well.
>>>
>>> Hence I think this patch is correct and allows memory hotplug in
>>> absence
>>> of NUMA configuration. It also would allow to use pc-dimm as
>>> replacement
>>> for initial memory for non-NUMA configs (which is on my TODO list)
>>>
>>> As for the Windows, QEMU has no idea what OS it would be running,
>>> I see 2 ways to solve issue:
>>> 1. user should know that memory hotplug on Windows requires NUMA
>>> machine
>>> and specify "-numa ..." option for this case.
>>> (I've discussed this with libvirt folks and was promised that
>>> if user enables memory hotplug, libvirt would provide "-numa"
>>> option
>>> to workaround Windows issue)
>>>
>>> 2. QEMU could unconditionally create single NUMA if memory hotplug is
>>> enabled. (but that should be enable only for 2.2 or late machines
>>> to avoid migration issues)
>>>
>> I prefer 2. I'll try to send patches for it if Zhang is also OK with it.
>>
>
> Yep, It is a good scheme to create a dummy NUMA unconditionally.
> But Igor has said there are migration issues for this scenario, do you
> know what's
> it? ;)
Not sure. This one ?
https://www.mail-archive.com/qemu-devel%40nongnu.org/msg249146.html
Thanks. :)
>
> .
>
next prev parent reply other threads:[~2014-09-23 10:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 10:39 [Qemu-devel] [PATCH 0/2] fix two bugs about numa _and_ hotplug memory feature zhanghailiang
2014-09-16 10:39 ` [Qemu-devel] [PATCH 1/2] pc-dimm: No numa option shouldn't break " zhanghailiang
2014-09-17 8:32 ` Hu Tao
2014-09-17 9:25 ` zhanghailiang
2014-09-17 10:00 ` Tang Chen
2014-09-17 10:19 ` Andrey Korolyov
2014-09-18 0:58 ` Hu Tao
2014-09-19 12:26 ` Igor Mammedov
2014-09-22 9:03 ` Tang Chen
2014-09-22 9:46 ` zhanghailiang
2014-09-23 8:40 ` Igor Mammedov
2014-09-23 8:58 ` Tang Chen
2014-09-23 10:11 ` zhanghailiang
2014-09-23 10:32 ` Tang Chen [this message]
2014-09-23 11:12 ` Igor Mammedov
2014-09-23 12:38 ` zhanghailiang
2014-09-19 12:37 ` Igor Mammedov
2014-09-22 11:17 ` Michael S. Tsirkin
2014-09-23 9:01 ` Igor Mammedov
2014-09-23 10:07 ` zhanghailiang
2014-09-23 11:13 ` Igor Mammedov
2014-09-16 10:39 ` [Qemu-devel] [PATCH 2/2] numa/pc-dimm: Fix stat of memory size in node when hotplug memory zhanghailiang
2014-09-16 11:20 ` Igor Mammedov
2014-09-17 8:22 ` zhanghailiang
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=54214C28.4080109@cn.fujitsu.com \
--to=tangchen@cn.fujitsu.com \
--cc=gaowanlong@cn.fujitsu.com \
--cc=hutao@cn.fujitsu.com \
--cc=imammedo@redhat.com \
--cc=luonengjun@huawei.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhang.zhanghailiang@huawei.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).