mirror of
https://github.com/cloud-hypervisor/cloud-hypervisor.git
synced 2025-03-20 07:58:55 +00:00
vmm: memory_manager: Remove _PXM from ACPI memory slot
The _PXM method always return 0, which is wrong since the SRAT might tell differently. The point of the _PXM method is to be evaluated by the guest OS when some new memory slot is being plugged, but this will never happen for Cloud Hypervisor since using NUMA nodes along with memory hotplug only works for virtio-mem. Memory hotplug through ACPI will only happen when there's only one NUMA node exposed to the guest, which means the _PXM method won't be needed at all. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
This commit is contained in:
parent
07f3075773
commit
09c3ddd47d
@ -1614,14 +1614,6 @@ impl Aml for MemorySlot {
|
||||
vec![&self.slot_id],
|
||||
))],
|
||||
),
|
||||
// We don't expose any NUMA characteristics so all memory is in the same "proximity domain"
|
||||
&aml::Method::new(
|
||||
"_PXM".into(),
|
||||
0,
|
||||
false,
|
||||
// We aren't NUMA so associate all RAM into the same proximity region (zero)
|
||||
vec![&aml::Return::new(&0u32)],
|
||||
),
|
||||
],
|
||||
)
|
||||
.to_aml_bytes()
|
||||
|
Loading…
x
Reference in New Issue
Block a user