From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Ladi Prosek <lprosek@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: [Qemu-devel] [PULL 12/13] pc: ACPI BIOS: use highest NUMA node for hotplug mem hole SRAT entry
Date: Mon, 29 May 2017 03:19:03 +0300 [thread overview]
Message-ID: <1496017081-24032-13-git-send-email-mst@redhat.com> (raw)
In-Reply-To: <1496017081-24032-1-git-send-email-mst@redhat.com>
From: Ladi Prosek <lprosek@redhat.com>
For reasons unknown, Windows won't online all memory, both at command
line and hot-plugged later, unless the hotplug mem hole SRAT entry
specifies a node greater than or equal to the ones where memory is
added.
Using the highest node on the machine makes recent versions of Windows
happy.
With this example command line:
... \
-m 1024,slots=4,maxmem=32G \
-numa node,nodeid=0 \
-numa node,nodeid=1 \
-numa node,nodeid=2 \
-numa node,nodeid=3 \
-object memory-backend-ram,size=1G,id=mem-mem1 \
-device pc-dimm,id=dimm-mem1,memdev=mem-mem1,node=1
Windows reports a total of 1G of RAM without this commit and the expected
2G with this commit.
Signed-off-by: Ladi Prosek <lprosek@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Acked-by: Laszlo Ersek <lersek@redhat.com>
---
hw/i386/acpi-build.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index afcadac..82bd44f 100644
--- a/hw/i386/acpi-build.c
+++ b/hw/i386/acpi-build.c
@@ -2404,14 +2404,17 @@ build_srat(GArray *table_data, BIOSLinker *linker, MachineState *machine)
}
/*
- * Entry is required for Windows to enable memory hotplug in OS.
+ * Entry is required for Windows to enable memory hotplug in OS
+ * and for Linux to enable SWIOTLB when booted with less than
+ * 4G of RAM. Windows works better if the entry sets proximity
+ * to the highest NUMA node in the machine.
* Memory devices may override proximity set by this entry,
* providing _PXM method if necessary.
*/
if (hotplugabble_address_space_size) {
numamem = acpi_data_push(table_data, sizeof *numamem);
build_srat_memory(numamem, pcms->hotplug_memory.base,
- hotplugabble_address_space_size, 0,
+ hotplugabble_address_space_size, pcms->numa_nodes - 1,
MEM_AFFINITY_HOTPLUGGABLE | MEM_AFFINITY_ENABLED);
}
--
MST
next prev parent reply other threads:[~2017-05-29 0:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 0:18 [Qemu-devel] [PULL 00/13] pci, virtio, vhost: fixes Michael S. Tsirkin
2017-05-29 0:18 ` [Qemu-devel] [PULL 01/13] memory: tune last param of iommu_ops.translate() Michael S. Tsirkin
2017-05-29 0:18 ` [Qemu-devel] [PULL 02/13] memory: remove the last param in memory_region_iommu_replay() Michael S. Tsirkin
2017-05-29 0:18 ` [Qemu-devel] [PULL 03/13] x86-iommu: use DeviceClass properties Michael S. Tsirkin
2017-05-29 0:18 ` [Qemu-devel] [PULL 04/13] intel_iommu: renaming context entry helpers Michael S. Tsirkin
2017-05-29 0:18 ` [Qemu-devel] [PULL 05/13] intel_iommu: provide vtd_ce_get_type() Michael S. Tsirkin
2017-05-29 0:18 ` [Qemu-devel] [PULL 06/13] intel_iommu: use IOMMU_ACCESS_FLAG() Michael S. Tsirkin
2017-05-29 0:18 ` [Qemu-devel] [PULL 07/13] intel_iommu: allow dev-iotlb context entry conditionally Michael S. Tsirkin
2017-05-29 0:18 ` [Qemu-devel] [PULL 09/13] intel_iommu: turn off pt before 2.9 Michael S. Tsirkin
2017-05-29 0:18 ` [Qemu-devel] [PULL 10/13] virtio_net: Bypass backends for MTU feature negotiation Michael S. Tsirkin
2017-05-29 0:18 ` [Qemu-devel] [PULL 11/13] vhost-user: pass message as a pointer to process_message_reply() Michael S. Tsirkin
2017-05-29 0:19 ` Michael S. Tsirkin [this message]
2017-05-29 0:19 ` [Qemu-devel] [PULL 13/13] acpi-test: update expected files Michael S. Tsirkin
2017-05-29 0:19 ` [Qemu-devel] [PULL 08/13] intel_iommu: support passthrough (PT) Michael S. Tsirkin
2017-05-30 9:41 ` [Qemu-devel] [PULL 00/13] pci, virtio, vhost: fixes Stefan Hajnoczi
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=1496017081-24032-13-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=lprosek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).