| commit | dce1b089249f52c053cf74dc3da98aea16656961 | |
| author | Yi Min Zhao <zyimin@linux.vnet.ibm.com> | |
| Wed, 28 Oct 2015 03:30:23 +0000 (28 11:30 +0800) | ||
| committer | Cornelia Huck <cornelia.huck@de.ibm.com> | |
| Wed, 11 Nov 2015 16:21:38 +0000 (11 17:21 +0100) | ||
| tree | 6d8da47f591a3f995eee4423b1eeecfd2b3fc0c9 | treesnapshot (tar.gz zip) |
| parent | b498484ed49ab9d1fcada3468f95dda1a5f59366 | commitdiff |
s390x/pci : fix up s390 pci iommu translation function
On s390x, each pci device has its own iommu, which is only properly
setup in qemu once the mpcifc instruction used to register the
translation table has been intercepted. Therefore, for a pci device that
is not configured or has not been initialized, proper translation is
neither required nor possible. Moreover, we may not have a host bridge
device ready yet.
This was exposed by a recent vfio change that triggers iommu translation
during the initialization of the vfio pci device. Let's do an early exit
in that case.
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Reviewed-by: Jens Freimann <jfrei@linux.vnet.ibm.com>
Signed-off-by: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
On s390x, each pci device has its own iommu, which is only properly
setup in qemu once the mpcifc instruction used to register the
translation table has been intercepted. Therefore, for a pci device that
is not configured or has not been initialized, proper translation is
neither required nor possible. Moreover, we may not have a host bridge
device ready yet.
This was exposed by a recent vfio change that triggers iommu translation
during the initialization of the vfio pci device. Let's do an early exit
in that case.
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Reviewed-by: Jens Freimann <jfrei@linux.vnet.ibm.com>
Signed-off-by: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
| hw/s390x/s390-pci-bus.c | diffblobblamehistory |