xref: /openbmc/linux/drivers/vfio/Kconfig (revision 6d99a79c)
1config VFIO_IOMMU_TYPE1
2	tristate
3	depends on VFIO
4	default n
5
6config VFIO_IOMMU_SPAPR_TCE
7	tristate
8	depends on VFIO && SPAPR_TCE_IOMMU
9	default VFIO
10
11config VFIO_SPAPR_EEH
12	tristate
13	depends on EEH && VFIO_IOMMU_SPAPR_TCE
14	default VFIO
15
16config VFIO_VIRQFD
17	tristate
18	depends on VFIO && EVENTFD
19	default n
20
21menuconfig VFIO
22	tristate "VFIO Non-Privileged userspace driver framework"
23	depends on IOMMU_API
24	select VFIO_IOMMU_TYPE1 if (X86 || S390 || ARM || ARM64)
25	select ANON_INODES
26	help
27	  VFIO provides a framework for secure userspace device drivers.
28	  See Documentation/vfio.txt for more details.
29
30	  If you don't know what to do here, say N.
31
32menuconfig VFIO_NOIOMMU
33	bool "VFIO No-IOMMU support"
34	depends on VFIO
35	help
36	  VFIO is built on the ability to isolate devices using the IOMMU.
37	  Only with an IOMMU can userspace access to DMA capable devices be
38	  considered secure.  VFIO No-IOMMU mode enables IOMMU groups for
39	  devices without IOMMU backing for the purpose of re-using the VFIO
40	  infrastructure in a non-secure mode.  Use of this mode will result
41	  in an unsupportable kernel and will therefore taint the kernel.
42	  Device assignment to virtual machines is also not possible with
43	  this mode since there is no IOMMU to provide DMA translation.
44
45	  If you don't know what to do here, say N.
46
47source "drivers/vfio/pci/Kconfig"
48source "drivers/vfio/platform/Kconfig"
49source "drivers/vfio/mdev/Kconfig"
50source "virt/lib/Kconfig"
51