On 13.12.2011, at 07:21, Matt Evans wrote: > Different architectures will deal with MMIO exits differently. For example, > KVM_EXIT_IO is x86-specific, and I/O cycles are often synthesised by steering > into windows in PCI bridges on other architectures. > > This patch calls arch-specific kvm_cpu__emulate_io() and kvm_cpu__emulate_mmio() > from the main runloop's IO and MMIO exit handlers. For x86, these directly > call kvm__emulate_io() and kvm__emulate_mmio() but other architectures will > perform some address munging before passing on the call. Why do you need address munging? PIO is simply not there and MMIO always goes to the physical address the CPU sees, so I don't see what you want to munge. The way the memory bus is attached to the CPU should certainly not be modeled differently for PPC and x86. Alex -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
