# SPDX-License-Identifier: GPL-2.0-only config [31mCONFIG_VFIO_IOMMU_TYPE1[0m tristate depends on [31mCONFIG_VFIO[0m default n config [31mCONFIG_VFIO_IOMMU_SPAPR_TCE[0m tristate depends on [31mCONFIG_VFIO[0m && [31mCONFIG_SPAPR_TCE_IOMMU[0m default [31mCONFIG_VFIO[0m config [31mCONFIG_VFIO_SPAPR_EEH[0m tristate depends on [31mCONFIG_EEH[0m && [31mCONFIG_VFIO_IOMMU_SPAPR_TCE[0m default [31mCONFIG_VFIO[0m config [31mCONFIG_VFIO_VIRQFD[0m tristate depends on [31mCONFIG_VFIO[0m && [31mCONFIG_EVENTFD[0m default n menuconfig [31mCONFIG_VFIO[0m tristate "VFIO Non-Privileged userspace driver framework" depends on [31mCONFIG_IOMMU_API[0m select [31mCONFIG_VFIO_IOMMU_TYPE1[0m if ([31mCONFIG_X86[0m || [31mCONFIG_S390[0m || [31mCONFIG_ARM[0m || [31mCONFIG_ARM64[0m) help [31mCONFIG_VFIO[0m provides a framework for secure userspace device drivers. See Documentation/driver-api/vfio.rst for more details. If you don't know what to do here, say N. menuconfig [31mCONFIG_VFIO_NOIOMMU[0m bool "VFIO No-IOMMU support" depends on [31mCONFIG_VFIO[0m help [31mCONFIG_VFIO[0m is built on the ability to isolate devices using the IOMMU. Only with an IOMMU can userspace access to DMA capable devices be considered secure. [31mCONFIG_VFIO[0m No-IOMMU mode enables IOMMU groups for devices without IOMMU backing for the purpose of re-using the [31mCONFIG_VFIO[0m infrastructure in a non-secure mode. Use of this mode will result in an unsupportable kernel and will therefore taint the kernel. Device assignment to virtual machines is also not possible with this mode since there is no IOMMU to provide DMA translation. If you don't know what to do here, say N. source "drivers/vfio/pci/Kconfig" source "drivers/vfio/platform/Kconfig" source "drivers/vfio/mdev/Kconfig" source "virt/lib/Kconfig" |