Alex Williamson 7c435b46c2 vfio: If an IOMMU backend fails, keep looking ... Consider an IOMMU to be an API rather than an implementation, we might have multiple implementations supporting the same API, so try another if one fails. The expectation here is that we'll really only have one implementation per device type. For instance the existing type1 driver works with any PCI device where the IOMMU API is available. A vGPU vendor may have a virtual PCI device which provides DMA isolation and mapping through other mechanisms, but can re-use userspaces that make use of the type1 VFIO IOMMU API. This allows that to work. Signed-off-by: Alex Williamson <alex.williamson@redhat.com>		2016-02-22 16:10:08 -07:00
..
pci	vfio/pci: Fix unsigned comparison overflow	2016-02-22 16:03:54 -07:00
platform	VFIO: platform: reset: fix a warning message condition	2015-12-21 15:28:11 -07:00
Kconfig	vfio: Include No-IOMMU mode	2015-12-21 15:28:11 -07:00
Makefile	vfio: Split virqfd into a separate module for vfio bus drivers	2015-03-17 08:33:38 -06:00
vfio_iommu_spapr_tce.c	vfio: powerpc/spapr: Support Dynamic DMA windows	2015-06-11 15:16:55 +10:00
vfio_iommu_type1.c	vfio/iommu_type1: make use of info.flags	2016-01-04 12:55:44 -07:00
vfio_spapr_eeh.c	drivers/vfio: Support EEH error injection	2015-05-12 20:33:35 +10:00
vfio.c	vfio: If an IOMMU backend fails, keep looking	2016-02-22 16:10:08 -07:00
virqfd.c	vfio: Split virqfd into a separate module for vfio bus drivers	2015-03-17 08:33:38 -06:00