Commit 82ea06e "Introduce KVM_VIRTIO_MMIO_AREA" did just that, but only for x86. Causing the following commit 5c301a3 "Add virtio-mmio support" to break the build for powerpc.
We follow what x86 did and place it 16MB past the PCI area, I have no idea if that is actually a good idea, or whether it works at all. Signed-off-by: Michael Ellerman <mich...@ellerman.id.au> --- I don't see any logic in pci_get_io_space_block() to stop it running into the VIRTIO area? But I haven't dug any further. --- tools/kvm/powerpc/include/kvm/kvm-arch.h | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/kvm/powerpc/include/kvm/kvm-arch.h b/tools/kvm/powerpc/include/kvm/kvm-arch.h index c7620b2..404e33e 100644 --- a/tools/kvm/powerpc/include/kvm/kvm-arch.h +++ b/tools/kvm/powerpc/include/kvm/kvm-arch.h @@ -39,6 +39,7 @@ * from. Note that this is a PCI bus address. */ #define KVM_PCI_MMIO_AREA 0x1000000 +#define KVM_VIRTIO_MMIO_AREA 0x2000000 struct spapr_phb; -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
