Following Alex's comment [1] on "Introduce hybrid CPU topology" RFC [2], this series strengthen a bit the CPU cluster by restricting it to a particular CPU type.
We'd rather have a single way of creating heterogeneous (hybrid) CPU topology. Note the CPU cluster is not user-creatable, so few more work is required in this area. Based-on: <20230216122524.67212-1-phi...@linaro.org> [3] "Have object_child_foreach() take Error* and return boolean" [1] https://lore.kernel.org/qemu-devel/87y1p1c18a....@linaro.org/ [2] https://lore.kernel.org/qemu-devel/20230213095035.158240-1-zhao1....@linux.intel.com/ [3] https://lore.kernel.org/qemu-devel/20230216122524.67212-1-phi...@linaro.org/ Philippe Mathieu-Daudé (5): hw/cpu: Extend CPUState::cluster_index documentation hw/cpu/cluster: Only add CPU objects to CPU cluster hw/cpu/cluster: Restrict CPU cluster to a particular CPU type hw/arm: Restrict CPU clusters to the expected type hw/riscv: Restrict CPU clusters to the expected type accel/tcg/tcg-accel-ops.c | 13 ++++++++++++- hw/arm/armsse.c | 1 + hw/arm/xlnx-zynqmp.c | 4 ++++ hw/cpu/cluster.c | 33 +++++++++++++++++++++++++++------ hw/riscv/microchip_pfsoc.c | 4 ++++ hw/riscv/sifive_u.c | 2 ++ include/hw/core/cpu.h | 2 ++ include/hw/cpu/cluster.h | 1 + 8 files changed, 53 insertions(+), 7 deletions(-) -- 2.38.1
