1 # SPDX-License-Identifier: GPL-2.0-only
2 # The IOVA library may also be used by non-IOMMU_API users
6 # 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
36 depends on !GENERIC_ATOMIC64 # for cmpxchg64()
38 Enable support for the ARM long descriptor pagetable format.
39 This allocator supports 4K/2M/1G, 16K/32M and 64K/512M page
40 sizes at both stage-1 and stage-2, as well as address spaces
41 up to 48-bits in size.
43 config IOMMU_IO_PGTABLE_LPAE_SELFTEST
45 depends on IOMMU_IO_PGTABLE_LPAE
47 Enable self-tests for LPAE page table allocator. This performs
48 a series of page-table consistency checks during boot.
50 If unsure, say N here.
52 config IOMMU_IO_PGTABLE_ARMV7S
53 bool "ARMv7/v8 Short Descriptor Format"
54 select IOMMU_IO_PGTABLE
55 depends on ARM || ARM64 || COMPILE_TEST
57 Enable support for the ARM Short-descriptor pagetable format.
58 This supports 32-bit virtual and physical addresses mapped using
59 2-level tables with 4KB pages/1MB sections, and contiguous entries
60 for 64KB pages/16MB supersections if indicated by the IOMMU driver.
62 config IOMMU_IO_PGTABLE_ARMV7S_SELFTEST
63 bool "ARMv7s selftests"
64 depends on IOMMU_IO_PGTABLE_ARMV7S
66 Enable self-tests for ARMv7s page table allocator. This performs
67 a series of page-table consistency checks during boot.
69 If unsure, say N here.
71 config IOMMU_IO_PGTABLE_DART
72 bool "Apple DART Formats"
73 select IOMMU_IO_PGTABLE
74 depends on ARM64 || COMPILE_TEST
75 depends on !GENERIC_ATOMIC64 # for cmpxchg64()
77 Enable support for the Apple DART pagetable formats. These include
78 the t8020 and t6000/t8110 DART formats used in Apple M1/M2 family
81 If unsure, say N here.
86 bool "Export IOMMU internals in DebugFS"
89 Allows exposure of IOMMU device internals. This option enables
90 the use of debugfs by IOMMU drivers as required. Devices can,
91 at initialization time, cause the IOMMU code to create a top-level
92 debug/iommu directory, and then populate a subdirectory with
96 prompt "IOMMU default domain type"
98 default IOMMU_DEFAULT_DMA_LAZY if X86 || S390
99 default IOMMU_DEFAULT_DMA_STRICT
101 Choose the type of IOMMU domain used to manage DMA API usage by
102 device drivers. The options here typically represent different
103 levels of tradeoff between robustness/security and performance,
104 depending on the IOMMU driver. Not all IOMMUs support all options.
105 This choice can be overridden at boot via the command line, and for
106 some devices also at runtime via sysfs.
108 If unsure, keep the default.
110 config IOMMU_DEFAULT_DMA_STRICT
111 bool "Translated - Strict"
113 Trusted devices use translation to restrict their access to only
114 DMA-mapped pages, with strict TLB invalidation on unmap. Equivalent
115 to passing "iommu.passthrough=0 iommu.strict=1" on the command line.
117 Untrusted devices always use this mode, with an additional layer of
118 bounce-buffering such that they cannot gain access to any unrelated
119 data within a mapped page.
121 config IOMMU_DEFAULT_DMA_LAZY
122 bool "Translated - Lazy"
124 Trusted devices use translation to restrict their access to only
125 DMA-mapped pages, but with "lazy" batched TLB invalidation. This
126 mode allows higher performance with some IOMMUs due to reduced TLB
127 flushing, but at the cost of reduced isolation since devices may be
128 able to access memory for some time after it has been unmapped.
129 Equivalent to passing "iommu.passthrough=0 iommu.strict=0" on the
132 If this mode is not supported by the IOMMU driver, the effective
133 runtime default will fall back to IOMMU_DEFAULT_DMA_STRICT.
135 config IOMMU_DEFAULT_PASSTHROUGH
138 Trusted devices are identity-mapped, giving them unrestricted access
139 to memory with minimal performance overhead. Equivalent to passing
140 "iommu.passthrough=1" (historically "iommu=pt") on the command line.
142 If this mode is not supported by the IOMMU driver, the effective
143 runtime default will fall back to IOMMU_DEFAULT_DMA_STRICT.
149 depends on OF && IOMMU_API
151 # IOMMU-agnostic DMA-mapping layer
153 def_bool ARM64 || X86 || S390
158 select NEED_SG_DMA_LENGTH
159 select NEED_SG_DMA_FLAGS if SWIOTLB
161 # Shared Virtual Addressing
170 bool "Freescale IOMMU support"
172 depends on PHYS_64BIT
173 depends on PPC_E500MC || (COMPILE_TEST && PPC)
175 select GENERIC_ALLOCATOR
177 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
178 PAMU can authorize memory access, remap the memory address, and remap I/O
183 bool "MSM IOMMU Support"
185 depends on ARCH_QCOM || COMPILE_TEST
187 select IOMMU_IO_PGTABLE_ARMV7S
189 Support for the IOMMUs found on certain Qualcomm SOCs.
190 These IOMMUs allow virtualization of the address space used by most
191 cores within the multimedia subsystem.
193 If unsure, say N here.
195 source "drivers/iommu/amd/Kconfig"
196 source "drivers/iommu/intel/Kconfig"
197 source "drivers/iommu/iommufd/Kconfig"
200 bool "Support for Interrupt Remapping"
201 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
202 select DMAR_TABLE if INTEL_IOMMU
204 Supports Interrupt remapping for IO-APIC and MSI devices.
205 To use x2apic mode in the CPU's which support x2APIC enhancements or
206 to support platforms with CPU's having > 8 bit APIC ID, say Y.
210 bool "OMAP IOMMU Support"
211 depends on ARCH_OMAP2PLUS || COMPILE_TEST
214 The OMAP3 media platform drivers depend on iommu support,
215 if you need them say Y here.
217 config OMAP_IOMMU_DEBUG
218 bool "Export OMAP IOMMU internals in DebugFS"
219 depends on OMAP_IOMMU && DEBUG_FS
221 Select this to see extensive information about
222 the internal state of OMAP IOMMU in debugfs.
224 Say N unless you know you need this.
226 config ROCKCHIP_IOMMU
227 bool "Rockchip IOMMU Support"
228 depends on ARCH_ROCKCHIP || COMPILE_TEST
230 select ARM_DMA_USE_IOMMU
232 Support for IOMMUs found on Rockchip rk32xx SOCs.
233 These IOMMUs allow virtualization of the address space used by most
234 cores within the multimedia subsystem.
235 Say Y here if you are using a Rockchip SoC that includes an IOMMU
239 bool "Allwinner H6 IOMMU Support"
241 depends on ARCH_SUNXI || COMPILE_TEST
242 select ARM_DMA_USE_IOMMU
245 Support for the IOMMU introduced in the Allwinner H6 SoCs.
247 config TEGRA_IOMMU_SMMU
248 bool "NVIDIA Tegra SMMU Support"
249 depends on ARCH_TEGRA
254 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
255 SoCs (Tegra30 up to Tegra210).
258 bool "Exynos IOMMU Support"
259 depends on ARCH_EXYNOS || COMPILE_TEST
260 depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes
262 select ARM_DMA_USE_IOMMU
264 Support for the IOMMU (System MMU) of Samsung Exynos application
265 processor family. This enables H/W multimedia accelerators to see
266 non-linear physical memory chunks as linear memory in their
269 If unsure, say N here.
271 config EXYNOS_IOMMU_DEBUG
272 bool "Debugging log for Exynos IOMMU"
273 depends on EXYNOS_IOMMU
275 Select this to see the detailed log message that shows what
276 happens in the IOMMU driver.
278 Say N unless you need kernel log message for IOMMU debugging.
281 bool "Renesas VMSA-compatible IPMMU"
282 depends on ARCH_RENESAS || COMPILE_TEST
283 depends on ARM || ARM64 || COMPILE_TEST
284 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
286 select IOMMU_IO_PGTABLE_LPAE
287 select ARM_DMA_USE_IOMMU
289 Support for the Renesas VMSA-compatible IPMMU found in the R-Mobile
290 APE6, R-Car Gen{2,3} and RZ/G{1,2} SoCs.
294 config SPAPR_TCE_IOMMU
295 bool "sPAPR TCE IOMMU Support"
296 depends on PPC_POWERNV || PPC_PSERIES
299 Enables bits of IOMMU API required by VFIO. The iommu_ops
300 is not implemented as it is not necessary for VFIO.
303 tristate "Apple DART IOMMU Support"
304 depends on ARCH_APPLE || COMPILE_TEST
305 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_DART
307 select IOMMU_IO_PGTABLE_DART
310 Support for Apple DART (Device Address Resolution Table) IOMMUs
311 found in Apple ARM SoCs like the M1.
312 This IOMMU is required for most peripherals using DMA to access
315 Say Y here if you are using an Apple SoC.
319 tristate "ARM Ltd. System MMU (SMMU) Support"
320 depends on ARM64 || ARM || COMPILE_TEST
321 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
323 select IOMMU_IO_PGTABLE_LPAE
324 select ARM_DMA_USE_IOMMU if ARM
326 Support for implementations of the ARM System MMU architecture
329 Say Y here if your SoC includes an IOMMU device implementing
330 the ARM SMMU architecture.
332 config ARM_SMMU_LEGACY_DT_BINDINGS
333 bool "Support the legacy \"mmu-masters\" devicetree bindings"
334 depends on ARM_SMMU=y && OF
336 Support for the badly designed and deprecated "mmu-masters"
337 devicetree bindings. This allows some DMA masters to attach
338 to the SMMU but does not provide any support via the DMA API.
339 If you're lucky, you might be able to get VFIO up and running.
341 If you say Y here then you'll make me very sad. Instead, say N
342 and move your firmware to the utopian future that was 2016.
344 config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT
345 bool "Default to disabling bypass on ARM SMMU v1 and v2"
349 Say Y here to (by default) disable bypass streams such that
350 incoming transactions from devices that are not attached to
351 an iommu domain will report an abort back to the device and
352 will not be allowed to pass through the SMMU.
354 Any old kernels that existed before this KConfig was
355 introduced would default to _allowing_ bypass (AKA the
356 equivalent of NO for this config). However the default for
357 this option is YES because the old behavior is insecure.
359 There are few reasons to allow unmatched stream bypass, and
360 even fewer good ones. If saying YES here breaks your board
361 you should work on fixing your board. This KConfig option
362 is expected to be removed in the future and we'll simply
363 hardcode the bypass disable in the code.
365 NOTE: the kernel command line parameter
366 'arm-smmu.disable_bypass' will continue to override this
371 depends on ARM_SMMU && ARCH_QCOM
374 When running on a Qualcomm platform that has the custom variant
375 of the ARM SMMU, this needs to be built into the SMMU driver.
377 config ARM_SMMU_QCOM_DEBUG
378 bool "ARM SMMU QCOM implementation defined debug support"
379 depends on ARM_SMMU_QCOM
381 Support for implementation specific debug features in ARM SMMU
382 hardware found in QTI platforms.
384 Say Y here to enable debug for issues such as TLB sync timeouts
385 which requires implementation defined register dumps.
388 tristate "ARM Ltd. System MMU Version 3 (SMMUv3) Support"
391 select IOMMU_IO_PGTABLE_LPAE
392 select GENERIC_MSI_IRQ
394 Support for implementations of the ARM System MMU architecture
395 version 3 providing translation support to a PCIe root complex.
397 Say Y here if your system includes an IOMMU device implementing
398 the ARM SMMUv3 architecture.
400 config ARM_SMMU_V3_SVA
401 bool "Shared Virtual Addressing support for the ARM SMMUv3"
402 depends on ARM_SMMU_V3
407 Support for sharing process address spaces with devices using the
410 Say Y here if your system supports SVA extensions such as PCIe PASID
414 def_bool y if S390 && PCI
415 depends on S390 && PCI
418 Support for the IOMMU API for s390 PCI devices.
421 tristate "MediaTek IOMMU Support"
422 depends on ARCH_MEDIATEK || COMPILE_TEST
423 select ARM_DMA_USE_IOMMU
425 select IOMMU_IO_PGTABLE_ARMV7S
429 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia
430 Memory Management Unit. This option enables remapping of DMA memory
431 accesses for the multimedia subsystem.
433 If unsure, say N here.
436 tristate "MediaTek IOMMU Version 1 (M4U gen1) Support"
438 depends on ARCH_MEDIATEK || COMPILE_TEST
439 select ARM_DMA_USE_IOMMU
444 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is
445 Multimedia Memory Managememt Unit. This option enables remapping of
446 DMA memory accesses for the multimedia subsystem.
448 if unsure, say N here.
451 # Note: iommu drivers cannot (yet?) be built as modules
452 bool "Qualcomm IOMMU Support"
453 depends on ARCH_QCOM || COMPILE_TEST
454 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
457 select IOMMU_IO_PGTABLE_LPAE
458 select ARM_DMA_USE_IOMMU
460 Support for IOMMU on certain Qualcomm SoCs.
463 bool "Hyper-V IRQ Handling"
464 depends on HYPERV && X86
468 Stub IOMMU driver to handle IRQs to support Hyper-V Linux
469 guest and root partitions.
472 tristate "Virtio IOMMU driver"
474 depends on (ARM64 || X86)
477 select ACPI_VIOT if ACPI
479 Para-virtualised IOMMU driver with virtio.
481 Say Y here if you intend to run this kernel as a guest.
484 tristate "Unisoc IOMMU Support"
485 depends on ARCH_SPRD || COMPILE_TEST
488 Support for IOMMU on Unisoc's SoCs, this IOMMU can be used by
489 Unisoc's multimedia devices, such as display, Image codec(jpeg)
490 and a few signal processors, including VSP(video), GSP(graphic),
491 ISP(image), and CPP(camera pixel processor), etc.
493 Say Y here if you want to use the multimedia devices listed above.
495 endif # IOMMU_SUPPORT