| Message ID | 20230223081401.248835-5-gshan@redhat.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | NUMA: Apply socket-NUMA-node boundary for aarch64 and RiscV machines | expand |
diff --git a/hw/riscv/spike.c b/hw/riscv/spike.c index cc3f6dac17..fba0cbec29 100644 --- a/hw/riscv/spike.c +++ b/hw/riscv/spike.c @@ -342,6 +342,7 @@ static void spike_board_init(MachineState *machine) static void spike_machine_instance_init(Object *obj) { + set_numa_socket_boundary(MACHINE(obj)); } static void spike_machine_class_init(ObjectClass *oc, void *data) diff --git a/hw/riscv/virt.c b/hw/riscv/virt.c index b81081c70b..ed79becb96 100644 --- a/hw/riscv/virt.c +++ b/hw/riscv/virt.c @@ -1521,6 +1521,7 @@ static void virt_machine_init(MachineState *machine) static void virt_machine_instance_init(Object *obj) { + set_numa_socket_boundary(MACHINE(obj)); } static char *virt_get_aia_guests(Object *obj, Error **errp)
There are two RISCV machines where NUMA is aware: 'virt' and 'spike'. 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/riscv/spike.c | 1 + hw/riscv/virt.c | 1 + 2 files changed, 2 insertions(+)