With KVM on Freescale booke parts we have currently two general types of virtual platforms-- 1) an 85xx-like platform with e500v2 cpus, etc, and 2) a P4080-like platform with a corenet based bus.
Today QEMU passes through to the guest a device tree with a top level compatible of either "MPC8544DS", or "fsl,P4080DS". These work but neither is quite accurate this is used on all targets regardless of the underlying physical hardware. Also, the guest device tree represents virtual devices as well as a subset of the cpus, memory, and devices on the hardware platform. So continuing to use "MPC8544DS" or "fsl,P4080DS" compatible for all QEMU/KVM created virtual machines is misleading and seems hackish. They are compatible to a degree, but the virtual platform would typically be quite different. What do you all think about creating some new somewhat generic machine types in Linux to represent these 2 types of virtual platforms. Perhaps: "MPC85xxDS" - for a virtual machine for the e500v2 type platforms and would support 85xx targets, plus P2020, P1022,etc "corenet-32-ds" - for a virtual machine similar to the 32-bit P4080 platforms "corenet-64-ds" - for a virtual machine based on a 64-bit corenet platform Thoughts? Thanks, Stuart Yoder _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev