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
167 bool "Freescale IOMMU support"
169 depends on PHYS_64BIT
170 depends on PPC_E500MC || (COMPILE_TEST && PPC)
172 select GENERIC_ALLOCATOR
174 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
175 PAMU can authorize memory access, remap the memory address, and remap I/O
180 bool "MSM IOMMU Support"
182 depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST
184 select IOMMU_IO_PGTABLE_ARMV7S
186 Support for the IOMMUs found on certain Qualcomm SOCs.
187 These IOMMUs allow virtualization of the address space used by most
188 cores within the multimedia subsystem.
190 If unsure, say N here.
192 source "drivers/iommu/amd/Kconfig"
193 source "drivers/iommu/intel/Kconfig"
194 source "drivers/iommu/iommufd/Kconfig"
197 bool "Support for Interrupt Remapping"
198 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
201 Supports Interrupt remapping for IO-APIC and MSI devices.
202 To use x2apic mode in the CPU's which support x2APIC enhancements or
203 to support platforms with CPU's having > 8 bit APIC ID, say Y.
207 bool "OMAP IOMMU Support"
208 depends on ARCH_OMAP2PLUS || COMPILE_TEST
211 The OMAP3 media platform drivers depend on iommu support,
212 if you need them say Y here.
214 config OMAP_IOMMU_DEBUG
215 bool "Export OMAP IOMMU internals in DebugFS"
216 depends on OMAP_IOMMU && DEBUG_FS
218 Select this to see extensive information about
219 the internal state of OMAP IOMMU in debugfs.
221 Say N unless you know you need this.
223 config ROCKCHIP_IOMMU
224 bool "Rockchip IOMMU Support"
225 depends on ARCH_ROCKCHIP || COMPILE_TEST
227 select ARM_DMA_USE_IOMMU
229 Support for IOMMUs found on Rockchip rk32xx SOCs.
230 These IOMMUs allow virtualization of the address space used by most
231 cores within the multimedia subsystem.
232 Say Y here if you are using a Rockchip SoC that includes an IOMMU
236 bool "Allwinner H6 IOMMU Support"
238 depends on ARCH_SUNXI || COMPILE_TEST
239 select ARM_DMA_USE_IOMMU
242 Support for the IOMMU introduced in the Allwinner H6 SoCs.
244 config TEGRA_IOMMU_SMMU
245 bool "NVIDIA Tegra SMMU Support"
246 depends on ARCH_TEGRA
251 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
252 SoCs (Tegra30 up to Tegra210).
255 bool "Exynos IOMMU Support"
256 depends on ARCH_EXYNOS || COMPILE_TEST
257 depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes
259 select ARM_DMA_USE_IOMMU
261 Support for the IOMMU (System MMU) of Samsung Exynos application
262 processor family. This enables H/W multimedia accelerators to see
263 non-linear physical memory chunks as linear memory in their
266 If unsure, say N here.
268 config EXYNOS_IOMMU_DEBUG
269 bool "Debugging log for Exynos IOMMU"
270 depends on EXYNOS_IOMMU
272 Select this to see the detailed log message that shows what
273 happens in the IOMMU driver.
275 Say N unless you need kernel log message for IOMMU debugging.
278 bool "Renesas VMSA-compatible IPMMU"
279 depends on ARCH_RENESAS || COMPILE_TEST
280 depends on ARM || ARM64 || COMPILE_TEST
281 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
283 select IOMMU_IO_PGTABLE_LPAE
284 select ARM_DMA_USE_IOMMU
286 Support for the Renesas VMSA-compatible IPMMU found in the R-Mobile
287 APE6, R-Car Gen{2,3} and RZ/G{1,2} SoCs.
291 config SPAPR_TCE_IOMMU
292 bool "sPAPR TCE IOMMU Support"
293 depends on PPC_POWERNV || PPC_PSERIES
296 Enables bits of IOMMU API required by VFIO. The iommu_ops
297 is not implemented as it is not necessary for VFIO.
300 tristate "Apple DART IOMMU Support"
301 depends on ARCH_APPLE || COMPILE_TEST
302 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_DART
304 select IOMMU_IO_PGTABLE_DART
307 Support for Apple DART (Device Address Resolution Table) IOMMUs
308 found in Apple ARM SoCs like the M1.
309 This IOMMU is required for most peripherals using DMA to access
312 Say Y here if you are using an Apple SoC.
316 tristate "ARM Ltd. System MMU (SMMU) Support"
317 depends on ARM64 || ARM || COMPILE_TEST
318 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
320 select IOMMU_IO_PGTABLE_LPAE
321 select ARM_DMA_USE_IOMMU if ARM
323 Support for implementations of the ARM System MMU architecture
326 Say Y here if your SoC includes an IOMMU device implementing
327 the ARM SMMU architecture.
329 config ARM_SMMU_LEGACY_DT_BINDINGS
330 bool "Support the legacy \"mmu-masters\" devicetree bindings"
331 depends on ARM_SMMU=y && OF
333 Support for the badly designed and deprecated "mmu-masters"
334 devicetree bindings. This allows some DMA masters to attach
335 to the SMMU but does not provide any support via the DMA API.
336 If you're lucky, you might be able to get VFIO up and running.
338 If you say Y here then you'll make me very sad. Instead, say N
339 and move your firmware to the utopian future that was 2016.
341 config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT
342 bool "Default to disabling bypass on ARM SMMU v1 and v2"
346 Say Y here to (by default) disable bypass streams such that
347 incoming transactions from devices that are not attached to
348 an iommu domain will report an abort back to the device and
349 will not be allowed to pass through the SMMU.
351 Any old kernels that existed before this KConfig was
352 introduced would default to _allowing_ bypass (AKA the
353 equivalent of NO for this config). However the default for
354 this option is YES because the old behavior is insecure.
356 There are few reasons to allow unmatched stream bypass, and
357 even fewer good ones. If saying YES here breaks your board
358 you should work on fixing your board. This KConfig option
359 is expected to be removed in the future and we'll simply
360 hardcode the bypass disable in the code.
362 NOTE: the kernel command line parameter
363 'arm-smmu.disable_bypass' will continue to override this
368 depends on ARM_SMMU && ARCH_QCOM
371 When running on a Qualcomm platform that has the custom variant
372 of the ARM SMMU, this needs to be built into the SMMU driver.
374 config ARM_SMMU_QCOM_DEBUG
375 bool "ARM SMMU QCOM implementation defined debug support"
376 depends on ARM_SMMU_QCOM
378 Support for implementation specific debug features in ARM SMMU
379 hardware found in QTI platforms.
381 Say Y here to enable debug for issues such as TLB sync timeouts
382 which requires implementation defined register dumps.
385 tristate "ARM Ltd. System MMU Version 3 (SMMUv3) Support"
388 select IOMMU_IO_PGTABLE_LPAE
389 select GENERIC_MSI_IRQ
391 Support for implementations of the ARM System MMU architecture
392 version 3 providing translation support to a PCIe root complex.
394 Say Y here if your system includes an IOMMU device implementing
395 the ARM SMMUv3 architecture.
397 config ARM_SMMU_V3_SVA
398 bool "Shared Virtual Addressing support for the ARM SMMUv3"
399 depends on ARM_SMMU_V3
403 Support for sharing process address spaces with devices using the
406 Say Y here if your system supports SVA extensions such as PCIe PASID
410 def_bool y if S390 && PCI
411 depends on S390 && PCI
414 Support for the IOMMU API for s390 PCI devices.
417 tristate "MediaTek IOMMU Support"
418 depends on ARCH_MEDIATEK || COMPILE_TEST
419 select ARM_DMA_USE_IOMMU
421 select IOMMU_IO_PGTABLE_ARMV7S
425 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia
426 Memory Management Unit. This option enables remapping of DMA memory
427 accesses for the multimedia subsystem.
429 If unsure, say N here.
432 tristate "MediaTek IOMMU Version 1 (M4U gen1) Support"
434 depends on ARCH_MEDIATEK || COMPILE_TEST
435 select ARM_DMA_USE_IOMMU
440 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is
441 Multimedia Memory Managememt Unit. This option enables remapping of
442 DMA memory accesses for the multimedia subsystem.
444 if unsure, say N here.
447 # Note: iommu drivers cannot (yet?) be built as modules
448 bool "Qualcomm IOMMU Support"
449 depends on ARCH_QCOM || COMPILE_TEST
450 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
453 select IOMMU_IO_PGTABLE_LPAE
454 select ARM_DMA_USE_IOMMU
456 Support for IOMMU on certain Qualcomm SoCs.
459 bool "Hyper-V IRQ Handling"
460 depends on HYPERV && X86
464 Stub IOMMU driver to handle IRQs to support Hyper-V Linux
465 guest and root partitions.
468 tristate "Virtio IOMMU driver"
470 depends on (ARM64 || X86)
473 select ACPI_VIOT if ACPI
475 Para-virtualised IOMMU driver with virtio.
477 Say Y here if you intend to run this kernel as a guest.
480 tristate "Unisoc IOMMU Support"
481 depends on ARCH_SPRD || COMPILE_TEST
484 Support for IOMMU on Unisoc's SoCs, this IOMMU can be used by
485 Unisoc's multimedia devices, such as display, Image codec(jpeg)
486 and a few signal processors, including VSP(video), GSP(graphic),
487 ISP(image), and CPP(camera pixel processor), etc.
489 Say Y here if you want to use the multimedia devices listed above.
491 endif # IOMMU_SUPPORT