@@ -844,6 +844,8 @@ static void sbsa_ref_instance_init(Object *obj)
SBSAMachineState *sms = SBSA_MACHINE(obj);
sbsa_flash_create(sms);
+
+ set_numa_socket_boundary(MACHINE(obj));
}
static void sbsa_ref_class_init(ObjectClass *oc, void *data)
@@ -3210,6 +3210,8 @@ static void virt_instance_init(Object *obj)
vms->oem_id = g_strndup(ACPI_BUILD_APPNAME6, 6);
vms->oem_table_id = g_strndup(ACPI_BUILD_APPNAME8, 8);
+
+ set_numa_socket_boundary(MACHINE(obj));
}
static const TypeInfo virt_machine_info = {
There are two ARM machines where NUMA is aware: 'virt' and 'sbsa-ref'. Both of them are required to follow socket-NUMA-node boundary. To enable the validation to reject incorrect configuration. Signed-off-by: Gavin Shan <gshan@redhat.com> --- hw/arm/sbsa-ref.c | 2 ++ hw/arm/virt.c | 2 ++ 2 files changed, 4 insertions(+)