diff options
| author |   Vitaly Kuznetsov <vkuznets@redhat.com> | 2021-12-16 10:58:26 +0100 |
|---|---|---|
| committer |   Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2021-12-17 19:10:55 +0100 |
| commit | bcf6f1759adff0ec3f73ab7b4a873405ee26ff5c (patch) | |
| tree | 6de7ed992c61dd55079aec3aec368bf14e75d8c3 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | Linux 5.16-rc5 (diff) | |
| download | wireguard-linux-bcf6f1759adff0ec3f73ab7b4a873405ee26ff5c.tar.xz wireguard-linux-bcf6f1759adff0ec3f73ab7b4a873405ee26ff5c.zip | |
ACPI: NUMA: Process hotpluggable memblocks when !CONFIG_MEMORY_HOTPLUG
Some systems (e.g. Hyper-V guests) have all their memory marked as
hotpluggable in SRAT. acpi_numa_memory_affinity_init(), however,
ignores all such regions when !CONFIG_MEMORY_HOTPLUG and this is
unfortunate as memory affinity (NUMA) information gets lost.
'Hot Pluggable' flag in SRAT only means that "system hardware supports
hot-add and hot-remove of this memory region", it doesn't prevent
memory from being cold-plugged there.
Ignore 'Hot Pluggable' bit instead of skipping the whole memory
affinity information when !CONFIG_MEMORY_HOTPLUG.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions