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.
70 config IOMMU_IO_PGTABLE_DART
71 bool "Apple DART Formats"
72 select IOMMU_IO_PGTABLE
73 depends on ARM64 || (COMPILE_TEST && !GENERIC_ATOMIC64)
75 Enable support for the Apple DART pagetable formats. These include
76 the t8020 and t6000/t8110 DART formats used in Apple M1/M2 family
79 If unsure, say N here.
84 bool "Export IOMMU internals in DebugFS"
87 Allows exposure of IOMMU device internals. This option enables
88 the use of debugfs by IOMMU drivers as required. Devices can,
89 at initialization time, cause the IOMMU code to create a top-level
90 debug/iommu directory, and then populate a subdirectory with
94 prompt "IOMMU default domain type"
96 default IOMMU_DEFAULT_DMA_LAZY if X86 || IA64
97 default IOMMU_DEFAULT_DMA_STRICT
99 Choose the type of IOMMU domain used to manage DMA API usage by
100 device drivers. The options here typically represent different
101 levels of tradeoff between robustness/security and performance,
102 depending on the IOMMU driver. Not all IOMMUs support all options.
103 This choice can be overridden at boot via the command line, and for
104 some devices also at runtime via sysfs.
106 If unsure, keep the default.
108 config IOMMU_DEFAULT_DMA_STRICT
109 bool "Translated - Strict"
111 Trusted devices use translation to restrict their access to only
112 DMA-mapped pages, with strict TLB invalidation on unmap. Equivalent
113 to passing "iommu.passthrough=0 iommu.strict=1" on the command line.
115 Untrusted devices always use this mode, with an additional layer of
116 bounce-buffering such that they cannot gain access to any unrelated
117 data within a mapped page.
119 config IOMMU_DEFAULT_DMA_LAZY
120 bool "Translated - Lazy"
122 Trusted devices use translation to restrict their access to only
123 DMA-mapped pages, but with "lazy" batched TLB invalidation. This
124 mode allows higher performance with some IOMMUs due to reduced TLB
125 flushing, but at the cost of reduced isolation since devices may be
126 able to access memory for some time after it has been unmapped.
127 Equivalent to passing "iommu.passthrough=0 iommu.strict=0" on the
130 If this mode is not supported by the IOMMU driver, the effective
131 runtime default will fall back to IOMMU_DEFAULT_DMA_STRICT.
133 config IOMMU_DEFAULT_PASSTHROUGH
136 Trusted devices are identity-mapped, giving them unrestricted access
137 to memory with minimal performance overhead. Equivalent to passing
138 "iommu.passthrough=1" (historically "iommu=pt") on the command line.
140 If this mode is not supported by the IOMMU driver, the effective
141 runtime default will fall back to IOMMU_DEFAULT_DMA_STRICT.
147 depends on OF && IOMMU_API
149 # IOMMU-agnostic DMA-mapping layer
151 def_bool ARM64 || IA64 || X86
156 select NEED_SG_DMA_LENGTH
158 # Shared Virtual Addressing
164 bool "Freescale IOMMU support"
166 depends on PHYS_64BIT
167 depends on PPC_E500MC || (COMPILE_TEST && PPC)
169 select GENERIC_ALLOCATOR
171 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
172 PAMU can authorize memory access, remap the memory address, and remap I/O
177 bool "MSM IOMMU Support"
179 depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST
181 select IOMMU_IO_PGTABLE_ARMV7S
183 Support for the IOMMUs found on certain Qualcomm SOCs.
184 These IOMMUs allow virtualization of the address space used by most
185 cores within the multimedia subsystem.
187 If unsure, say N here.
189 source "drivers/iommu/amd/Kconfig"
190 source "drivers/iommu/intel/Kconfig"
191 source "drivers/iommu/iommufd/Kconfig"
194 bool "Support for Interrupt Remapping"
195 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
198 Supports Interrupt remapping for IO-APIC and MSI devices.
199 To use x2apic mode in the CPU's which support x2APIC enhancements or
200 to support platforms with CPU's having > 8 bit APIC ID, say Y.
204 bool "OMAP IOMMU Support"
205 depends on ARCH_OMAP2PLUS || COMPILE_TEST
208 The OMAP3 media platform drivers depend on iommu support,
209 if you need them say Y here.
211 config OMAP_IOMMU_DEBUG
212 bool "Export OMAP IOMMU internals in DebugFS"
213 depends on OMAP_IOMMU && DEBUG_FS
215 Select this to see extensive information about
216 the internal state of OMAP IOMMU in debugfs.
218 Say N unless you know you need this.
220 config ROCKCHIP_IOMMU
221 bool "Rockchip IOMMU Support"
222 depends on ARCH_ROCKCHIP || COMPILE_TEST
224 select ARM_DMA_USE_IOMMU
226 Support for IOMMUs found on Rockchip rk32xx SOCs.
227 These IOMMUs allow virtualization of the address space used by most
228 cores within the multimedia subsystem.
229 Say Y here if you are using a Rockchip SoC that includes an IOMMU
233 bool "Allwinner H6 IOMMU Support"
235 depends on ARCH_SUNXI || COMPILE_TEST
236 select ARM_DMA_USE_IOMMU
239 Support for the IOMMU introduced in the Allwinner H6 SoCs.
241 config TEGRA_IOMMU_GART
242 bool "Tegra GART IOMMU Support"
243 depends on ARCH_TEGRA_2x_SOC
247 Enables support for remapping discontiguous physical memory
248 shared with the operating system into contiguous I/O virtual
249 space through the GART (Graphics Address Relocation Table)
250 hardware included on Tegra SoCs.
252 config TEGRA_IOMMU_SMMU
253 bool "NVIDIA Tegra SMMU Support"
254 depends on ARCH_TEGRA
259 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
260 SoCs (Tegra30 up to Tegra210).
263 bool "Exynos IOMMU Support"
264 depends on ARCH_EXYNOS || COMPILE_TEST
265 depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes
267 select ARM_DMA_USE_IOMMU
269 Support for the IOMMU (System MMU) of Samsung Exynos application
270 processor family. This enables H/W multimedia accelerators to see
271 non-linear physical memory chunks as linear memory in their
274 If unsure, say N here.
276 config EXYNOS_IOMMU_DEBUG
277 bool "Debugging log for Exynos IOMMU"
278 depends on EXYNOS_IOMMU
280 Select this to see the detailed log message that shows what
281 happens in the IOMMU driver.
283 Say N unless you need kernel log message for IOMMU debugging.
286 bool "Renesas VMSA-compatible IPMMU"
287 depends on ARCH_RENESAS || (COMPILE_TEST && !GENERIC_ATOMIC64)
289 select IOMMU_IO_PGTABLE_LPAE
290 select ARM_DMA_USE_IOMMU
292 Support for the Renesas VMSA-compatible IPMMU found in the R-Mobile
293 APE6, R-Car Gen{2,3} and RZ/G{1,2} SoCs.
297 config SPAPR_TCE_IOMMU
298 bool "sPAPR TCE IOMMU Support"
299 depends on PPC_POWERNV || PPC_PSERIES
302 Enables bits of IOMMU API required by VFIO. The iommu_ops
303 is not implemented as it is not necessary for VFIO.
306 tristate "Apple DART IOMMU Support"
307 depends on ARCH_APPLE || (COMPILE_TEST && !GENERIC_ATOMIC64)
309 select IOMMU_IO_PGTABLE_DART
312 Support for Apple DART (Device Address Resolution Table) IOMMUs
313 found in Apple ARM SoCs like the M1.
314 This IOMMU is required for most peripherals using DMA to access
317 Say Y here if you are using an Apple SoC.
321 tristate "ARM Ltd. System MMU (SMMU) Support"
322 depends on ARM64 || ARM || (COMPILE_TEST && !GENERIC_ATOMIC64)
324 select IOMMU_IO_PGTABLE_LPAE
325 select ARM_DMA_USE_IOMMU if ARM
327 Support for implementations of the ARM System MMU architecture
330 Say Y here if your SoC includes an IOMMU device implementing
331 the ARM SMMU architecture.
333 config ARM_SMMU_LEGACY_DT_BINDINGS
334 bool "Support the legacy \"mmu-masters\" devicetree bindings"
335 depends on ARM_SMMU=y && OF
337 Support for the badly designed and deprecated "mmu-masters"
338 devicetree bindings. This allows some DMA masters to attach
339 to the SMMU but does not provide any support via the DMA API.
340 If you're lucky, you might be able to get VFIO up and running.
342 If you say Y here then you'll make me very sad. Instead, say N
343 and move your firmware to the utopian future that was 2016.
345 config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT
346 bool "Default to disabling bypass on ARM SMMU v1 and v2"
350 Say Y here to (by default) disable bypass streams such that
351 incoming transactions from devices that are not attached to
352 an iommu domain will report an abort back to the device and
353 will not be allowed to pass through the SMMU.
355 Any old kernels that existed before this KConfig was
356 introduced would default to _allowing_ bypass (AKA the
357 equivalent of NO for this config). However the default for
358 this option is YES because the old behavior is insecure.
360 There are few reasons to allow unmatched stream bypass, and
361 even fewer good ones. If saying YES here breaks your board
362 you should work on fixing your board. This KConfig option
363 is expected to be removed in the future and we'll simply
364 hardcode the bypass disable in the code.
366 NOTE: the kernel command line parameter
367 'arm-smmu.disable_bypass' will continue to override this
372 depends on ARM_SMMU && ARCH_QCOM
375 When running on a Qualcomm platform that has the custom variant
376 of the ARM SMMU, this needs to be built into the SMMU driver.
378 config ARM_SMMU_QCOM_DEBUG
379 bool "ARM SMMU QCOM implementation defined debug support"
380 depends on ARM_SMMU_QCOM
382 Support for implementation specific debug features in ARM SMMU
383 hardware found in QTI platforms.
385 Say Y here to enable debug for issues such as TLB sync timeouts
386 which requires implementation defined register dumps.
389 tristate "ARM Ltd. System MMU Version 3 (SMMUv3) Support"
392 select IOMMU_IO_PGTABLE_LPAE
393 select GENERIC_MSI_IRQ
395 Support for implementations of the ARM System MMU architecture
396 version 3 providing translation support to a PCIe root complex.
398 Say Y here if your system includes an IOMMU device implementing
399 the ARM SMMUv3 architecture.
401 config ARM_SMMU_V3_SVA
402 bool "Shared Virtual Addressing support for the ARM SMMUv3"
403 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.
420 config S390_CCW_IOMMU
421 bool "S390 CCW IOMMU Support"
422 depends on S390 && CCW || COMPILE_TEST
425 Enables bits of IOMMU API required by VFIO. The iommu_ops
426 is not implemented as it is not necessary for VFIO.
429 bool "S390 AP IOMMU Support"
430 depends on S390 && ZCRYPT || COMPILE_TEST
433 Enables bits of IOMMU API required by VFIO. The iommu_ops
434 is not implemented as it is not necessary for VFIO.
437 tristate "MediaTek IOMMU Support"
438 depends on ARCH_MEDIATEK || COMPILE_TEST
439 select ARM_DMA_USE_IOMMU
441 select IOMMU_IO_PGTABLE_ARMV7S
445 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia
446 Memory Management Unit. This option enables remapping of DMA memory
447 accesses for the multimedia subsystem.
449 If unsure, say N here.
452 tristate "MediaTek IOMMU Version 1 (M4U gen1) Support"
454 depends on ARCH_MEDIATEK || COMPILE_TEST
455 select ARM_DMA_USE_IOMMU
460 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is
461 Multimedia Memory Managememt Unit. This option enables remapping of
462 DMA memory accesses for the multimedia subsystem.
464 if unsure, say N here.
467 # Note: iommu drivers cannot (yet?) be built as modules
468 bool "Qualcomm IOMMU Support"
469 depends on ARCH_QCOM || (COMPILE_TEST && !GENERIC_ATOMIC64)
472 select IOMMU_IO_PGTABLE_LPAE
473 select ARM_DMA_USE_IOMMU
475 Support for IOMMU on certain Qualcomm SoCs.
478 bool "Hyper-V IRQ Handling"
479 depends on HYPERV && X86
483 Stub IOMMU driver to handle IRQs to support Hyper-V Linux
484 guest and root partitions.
487 tristate "Virtio IOMMU driver"
489 depends on (ARM64 || X86)
492 select ACPI_VIOT if ACPI
494 Para-virtualised IOMMU driver with virtio.
496 Say Y here if you intend to run this kernel as a guest.
499 tristate "Unisoc IOMMU Support"
500 depends on ARCH_SPRD || COMPILE_TEST
503 Support for IOMMU on Unisoc's SoCs, this IOMMU can be used by
504 Unisoc's multimedia devices, such as display, Image codec(jpeg)
505 and a few signal processors, including VSP(video), GSP(graphic),
506 ISP(image), and CPP(camera pixel processor), etc.
508 Say Y here if you want to use the multimedia devices listed above.
510 endif # IOMMU_SUPPORT