1 # SPDX-License-Identifier: GPL-2.0-only
2 # The IOVA library may also be used by non-IOMMU_API users
6 # The IOASID library may also be used by non-IOMMU_API users
10 # IOMMU_API always gets selected by whoever wants it.
14 menuconfig IOMMU_SUPPORT
15 bool "IOMMU Hardware Support"
19 Say Y here if you want to compile device drivers for IO Memory
20 Management Units into the kernel. These devices usually allow to
21 remap DMA requests and/or remap interrupts from other devices on the
26 menu "Generic IOMMU Pagetable Support"
28 # Selected by the actual pagetable implementations
29 config IOMMU_IO_PGTABLE
32 config IOMMU_IO_PGTABLE_LPAE
33 bool "ARMv7/v8 Long Descriptor Format"
34 select IOMMU_IO_PGTABLE
35 depends on ARM || ARM64 || (COMPILE_TEST && !GENERIC_ATOMIC64)
37 Enable support for the ARM long descriptor pagetable format.
38 This allocator supports 4K/2M/1G, 16K/32M and 64K/512M page
39 sizes at both stage-1 and stage-2, as well as address spaces
40 up to 48-bits in size.
42 config IOMMU_IO_PGTABLE_LPAE_SELFTEST
44 depends on IOMMU_IO_PGTABLE_LPAE
46 Enable self-tests for LPAE page table allocator. This performs
47 a series of page-table consistency checks during boot.
49 If unsure, say N here.
51 config IOMMU_IO_PGTABLE_ARMV7S
52 bool "ARMv7/v8 Short Descriptor Format"
53 select IOMMU_IO_PGTABLE
54 depends on ARM || ARM64 || COMPILE_TEST
56 Enable support for the ARM Short-descriptor pagetable format.
57 This supports 32-bit virtual and physical addresses mapped using
58 2-level tables with 4KB pages/1MB sections, and contiguous entries
59 for 64KB pages/16MB supersections if indicated by the IOMMU driver.
61 config IOMMU_IO_PGTABLE_ARMV7S_SELFTEST
62 bool "ARMv7s selftests"
63 depends on IOMMU_IO_PGTABLE_ARMV7S
65 Enable self-tests for ARMv7s page table allocator. This performs
66 a series of page-table consistency checks during boot.
68 If unsure, say N here.
73 bool "Export IOMMU internals in DebugFS"
76 Allows exposure of IOMMU device internals. This option enables
77 the use of debugfs by IOMMU drivers as required. Devices can,
78 at initialization time, cause the IOMMU code to create a top-level
79 debug/iommu directory, and then populate a subdirectory with
83 prompt "IOMMU default domain type"
85 default IOMMU_DEFAULT_DMA_LAZY if X86 || IA64
86 default IOMMU_DEFAULT_DMA_STRICT
88 Choose the type of IOMMU domain used to manage DMA API usage by
89 device drivers. The options here typically represent different
90 levels of tradeoff between robustness/security and performance,
91 depending on the IOMMU driver. Not all IOMMUs support all options.
92 This choice can be overridden at boot via the command line, and for
93 some devices also at runtime via sysfs.
95 If unsure, keep the default.
97 config IOMMU_DEFAULT_DMA_STRICT
98 bool "Translated - Strict"
100 Trusted devices use translation to restrict their access to only
101 DMA-mapped pages, with strict TLB invalidation on unmap. Equivalent
102 to passing "iommu.passthrough=0 iommu.strict=1" on the command line.
104 Untrusted devices always use this mode, with an additional layer of
105 bounce-buffering such that they cannot gain access to any unrelated
106 data within a mapped page.
108 config IOMMU_DEFAULT_DMA_LAZY
109 bool "Translated - Lazy"
111 Trusted devices use translation to restrict their access to only
112 DMA-mapped pages, but with "lazy" batched TLB invalidation. This
113 mode allows higher performance with some IOMMUs due to reduced TLB
114 flushing, but at the cost of reduced isolation since devices may be
115 able to access memory for some time after it has been unmapped.
116 Equivalent to passing "iommu.passthrough=0 iommu.strict=0" on the
119 If this mode is not supported by the IOMMU driver, the effective
120 runtime default will fall back to IOMMU_DEFAULT_DMA_STRICT.
122 config IOMMU_DEFAULT_PASSTHROUGH
125 Trusted devices are identity-mapped, giving them unrestricted access
126 to memory with minimal performance overhead. Equivalent to passing
127 "iommu.passthrough=1" (historically "iommu=pt") on the command line.
129 If this mode is not supported by the IOMMU driver, the effective
130 runtime default will fall back to IOMMU_DEFAULT_DMA_STRICT.
136 depends on OF && IOMMU_API
138 # IOMMU-agnostic DMA-mapping layer
145 select NEED_SG_DMA_LENGTH
147 # Shared Virtual Addressing
153 bool "Freescale IOMMU support"
155 depends on PHYS_64BIT
156 depends on PPC_E500MC || (COMPILE_TEST && PPC)
158 select GENERIC_ALLOCATOR
160 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
161 PAMU can authorize memory access, remap the memory address, and remap I/O
166 bool "MSM IOMMU Support"
168 depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST
170 select IOMMU_IO_PGTABLE_ARMV7S
172 Support for the IOMMUs found on certain Qualcomm SOCs.
173 These IOMMUs allow virtualization of the address space used by most
174 cores within the multimedia subsystem.
176 If unsure, say N here.
178 source "drivers/iommu/amd/Kconfig"
179 source "drivers/iommu/intel/Kconfig"
182 bool "Support for Interrupt Remapping"
183 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
186 Supports Interrupt remapping for IO-APIC and MSI devices.
187 To use x2apic mode in the CPU's which support x2APIC enhancements or
188 to support platforms with CPU's having > 8 bit APIC ID, say Y.
192 bool "OMAP IOMMU Support"
193 depends on ARCH_OMAP2PLUS || COMPILE_TEST
196 The OMAP3 media platform drivers depend on iommu support,
197 if you need them say Y here.
199 config OMAP_IOMMU_DEBUG
200 bool "Export OMAP IOMMU internals in DebugFS"
201 depends on OMAP_IOMMU && DEBUG_FS
203 Select this to see extensive information about
204 the internal state of OMAP IOMMU in debugfs.
206 Say N unless you know you need this.
208 config ROCKCHIP_IOMMU
209 bool "Rockchip IOMMU Support"
210 depends on ARCH_ROCKCHIP || COMPILE_TEST
212 select ARM_DMA_USE_IOMMU
214 Support for IOMMUs found on Rockchip rk32xx SOCs.
215 These IOMMUs allow virtualization of the address space used by most
216 cores within the multimedia subsystem.
217 Say Y here if you are using a Rockchip SoC that includes an IOMMU
221 bool "Allwinner H6 IOMMU Support"
223 depends on ARCH_SUNXI || COMPILE_TEST
224 select ARM_DMA_USE_IOMMU
227 Support for the IOMMU introduced in the Allwinner H6 SoCs.
229 config TEGRA_IOMMU_GART
230 bool "Tegra GART IOMMU Support"
231 depends on ARCH_TEGRA_2x_SOC
235 Enables support for remapping discontiguous physical memory
236 shared with the operating system into contiguous I/O virtual
237 space through the GART (Graphics Address Relocation Table)
238 hardware included on Tegra SoCs.
240 config TEGRA_IOMMU_SMMU
241 bool "NVIDIA Tegra SMMU Support"
242 depends on ARCH_TEGRA
247 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
248 SoCs (Tegra30 up to Tegra210).
251 bool "Exynos IOMMU Support"
252 depends on ARCH_EXYNOS || COMPILE_TEST
253 depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes
255 select ARM_DMA_USE_IOMMU
257 Support for the IOMMU (System MMU) of Samsung Exynos application
258 processor family. This enables H/W multimedia accelerators to see
259 non-linear physical memory chunks as linear memory in their
262 If unsure, say N here.
264 config EXYNOS_IOMMU_DEBUG
265 bool "Debugging log for Exynos IOMMU"
266 depends on EXYNOS_IOMMU
268 Select this to see the detailed log message that shows what
269 happens in the IOMMU driver.
271 Say N unless you need kernel log message for IOMMU debugging.
274 bool "Renesas VMSA-compatible IPMMU"
275 depends on ARCH_RENESAS || (COMPILE_TEST && !GENERIC_ATOMIC64)
277 select IOMMU_IO_PGTABLE_LPAE
278 select ARM_DMA_USE_IOMMU
280 Support for the Renesas VMSA-compatible IPMMU found in the R-Mobile
281 APE6, R-Car Gen{2,3} and RZ/G{1,2} SoCs.
285 config SPAPR_TCE_IOMMU
286 bool "sPAPR TCE IOMMU Support"
287 depends on PPC_POWERNV || PPC_PSERIES
290 Enables bits of IOMMU API required by VFIO. The iommu_ops
291 is not implemented as it is not necessary for VFIO.
294 tristate "Apple DART IOMMU Support"
295 depends on ARCH_APPLE || (COMPILE_TEST && !GENERIC_ATOMIC64)
297 select IOMMU_IO_PGTABLE_LPAE
300 Support for Apple DART (Device Address Resolution Table) IOMMUs
301 found in Apple ARM SoCs like the M1.
302 This IOMMU is required for most peripherals using DMA to access
305 Say Y here if you are using an Apple SoC.
309 tristate "ARM Ltd. System MMU (SMMU) Support"
310 depends on ARM64 || ARM || (COMPILE_TEST && !GENERIC_ATOMIC64)
312 select IOMMU_IO_PGTABLE_LPAE
313 select ARM_DMA_USE_IOMMU if ARM
315 Support for implementations of the ARM System MMU architecture
318 Say Y here if your SoC includes an IOMMU device implementing
319 the ARM SMMU architecture.
321 config ARM_SMMU_LEGACY_DT_BINDINGS
322 bool "Support the legacy \"mmu-masters\" devicetree bindings"
323 depends on ARM_SMMU=y && OF
325 Support for the badly designed and deprecated "mmu-masters"
326 devicetree bindings. This allows some DMA masters to attach
327 to the SMMU but does not provide any support via the DMA API.
328 If you're lucky, you might be able to get VFIO up and running.
330 If you say Y here then you'll make me very sad. Instead, say N
331 and move your firmware to the utopian future that was 2016.
333 config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT
334 bool "Default to disabling bypass on ARM SMMU v1 and v2"
338 Say Y here to (by default) disable bypass streams such that
339 incoming transactions from devices that are not attached to
340 an iommu domain will report an abort back to the device and
341 will not be allowed to pass through the SMMU.
343 Any old kernels that existed before this KConfig was
344 introduced would default to _allowing_ bypass (AKA the
345 equivalent of NO for this config). However the default for
346 this option is YES because the old behavior is insecure.
348 There are few reasons to allow unmatched stream bypass, and
349 even fewer good ones. If saying YES here breaks your board
350 you should work on fixing your board. This KConfig option
351 is expected to be removed in the future and we'll simply
352 hardcode the bypass disable in the code.
354 NOTE: the kernel command line parameter
355 'arm-smmu.disable_bypass' will continue to override this
360 depends on ARM_SMMU && ARCH_QCOM
363 When running on a Qualcomm platform that has the custom variant
364 of the ARM SMMU, this needs to be built into the SMMU driver.
367 tristate "ARM Ltd. System MMU Version 3 (SMMUv3) Support"
370 select IOMMU_IO_PGTABLE_LPAE
371 select GENERIC_MSI_IRQ_DOMAIN
373 Support for implementations of the ARM System MMU architecture
374 version 3 providing translation support to a PCIe root complex.
376 Say Y here if your system includes an IOMMU device implementing
377 the ARM SMMUv3 architecture.
379 config ARM_SMMU_V3_SVA
380 bool "Shared Virtual Addressing support for the ARM SMMUv3"
381 depends on ARM_SMMU_V3
385 Support for sharing process address spaces with devices using the
388 Say Y here if your system supports SVA extensions such as PCIe PASID
392 def_bool y if S390 && PCI
393 depends on S390 && PCI
396 Support for the IOMMU API for s390 PCI devices.
398 config S390_CCW_IOMMU
399 bool "S390 CCW IOMMU Support"
400 depends on S390 && CCW || COMPILE_TEST
403 Enables bits of IOMMU API required by VFIO. The iommu_ops
404 is not implemented as it is not necessary for VFIO.
407 bool "S390 AP IOMMU Support"
408 depends on S390 && ZCRYPT || COMPILE_TEST
411 Enables bits of IOMMU API required by VFIO. The iommu_ops
412 is not implemented as it is not necessary for VFIO.
415 tristate "MediaTek IOMMU Support"
416 depends on ARCH_MEDIATEK || COMPILE_TEST
417 select ARM_DMA_USE_IOMMU
419 select IOMMU_IO_PGTABLE_ARMV7S
423 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia
424 Memory Management Unit. This option enables remapping of DMA memory
425 accesses for the multimedia subsystem.
427 If unsure, say N here.
430 tristate "MediaTek IOMMU Version 1 (M4U gen1) Support"
432 depends on ARCH_MEDIATEK || COMPILE_TEST
433 select ARM_DMA_USE_IOMMU
438 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is
439 Multimedia Memory Managememt Unit. This option enables remapping of
440 DMA memory accesses for the multimedia subsystem.
442 if unsure, say N here.
445 # Note: iommu drivers cannot (yet?) be built as modules
446 bool "Qualcomm IOMMU Support"
447 depends on ARCH_QCOM || (COMPILE_TEST && !GENERIC_ATOMIC64)
450 select IOMMU_IO_PGTABLE_LPAE
451 select ARM_DMA_USE_IOMMU
453 Support for IOMMU on certain Qualcomm SoCs.
456 bool "Hyper-V x2APIC IRQ Handling"
457 depends on HYPERV && X86
461 Stub IOMMU driver to handle IRQs as to allow Hyper-V Linux
462 guests to run with x2APIC mode enabled.
465 tristate "Virtio IOMMU driver"
467 depends on (ARM64 || X86)
471 select ACPI_VIOT if ACPI
473 Para-virtualised IOMMU driver with virtio.
475 Say Y here if you intend to run this kernel as a guest.
478 tristate "Unisoc IOMMU Support"
479 depends on ARCH_SPRD || COMPILE_TEST
482 Support for IOMMU on Unisoc's SoCs, this IOMMU can be used by
483 Unisoc's multimedia devices, such as display, Image codec(jpeg)
484 and a few signal processors, including VSP(video), GSP(graphic),
485 ISP(image), and CPP(camera pixel processor), etc.
487 Say Y here if you want to use the multimedia devices listed above.
489 endif # IOMMU_SUPPORT