Please don't top post. On 08.06.2012, at 09:55, Fei K Chen wrote: > I know that when simulating x86, kvm is using the "halt" instruction in guest OS to trap the VM idle, and then return to qemu to simulate I/O input for VM. > Is there any suitable instruction in ppc platform like "halt" in x86? The actual idle call is implementation specific. Some implementations use MSR_POW, but I don't know what A2 does. Check your spec for details :). > kvm should not return to qemu when emulating all of the private instructions. Kvm does not return to QEMU for emulation of instructions, except for MMIO. > Teaching prism platform in linux kernel to use MPIC and teaching Qemu to use XICS are two choices for us. And finally we decide to teaching Qemu to use XICS. Ah, A2 has an XICS? Nice :). We could certainly use emulation for that one, yeah. > There is something to do to write a correct device-tree used in qemu for our platform. Any suggestions for us? thanks. For prototyping, keep the device tree external - it makes your development cycles shorter. Once you know what to put in and you know that everything works just fine, you can move the device tree generation into QEMU, like we're doing for e500 now. Unless you're really into libfdt of course - then you can start off with the in-QEMU generation like David did :). Alex -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
