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.
10 menuconfig IOMMU_SUPPORT
11 bool "IOMMU Hardware Support"
15 Say Y here if you want to compile device drivers for IO Memory
16 Management Units into the kernel. These devices usually allow to
17 remap DMA requests and/or remap interrupts from other devices on the
22 menu "Generic IOMMU Pagetable Support"
24 # Selected by the actual pagetable implementations
25 config IOMMU_IO_PGTABLE
28 config IOMMU_IO_PGTABLE_LPAE
29 bool "ARMv7/v8 Long Descriptor Format"
30 select IOMMU_IO_PGTABLE
31 depends on ARM || ARM64 || COMPILE_TEST
32 depends on !GENERIC_ATOMIC64 # for cmpxchg64()
34 Enable support for the ARM long descriptor pagetable format.
35 This allocator supports 4K/2M/1G, 16K/32M and 64K/512M page
36 sizes at both stage-1 and stage-2, as well as address spaces
37 up to 48-bits in size.
39 config IOMMU_IO_PGTABLE_LPAE_SELFTEST
41 depends on IOMMU_IO_PGTABLE_LPAE
43 Enable self-tests for LPAE page table allocator. This performs
44 a series of page-table consistency checks during boot.
46 If unsure, say N here.
48 config IOMMU_IO_PGTABLE_ARMV7S
49 bool "ARMv7/v8 Short Descriptor Format"
50 select IOMMU_IO_PGTABLE
51 depends on ARM || ARM64 || COMPILE_TEST
53 Enable support for the ARM Short-descriptor pagetable format.
54 This supports 32-bit virtual and physical addresses mapped using
55 2-level tables with 4KB pages/1MB sections, and contiguous entries
56 for 64KB pages/16MB supersections if indicated by the IOMMU driver.
58 config IOMMU_IO_PGTABLE_ARMV7S_SELFTEST
59 bool "ARMv7s selftests"
60 depends on IOMMU_IO_PGTABLE_ARMV7S
62 Enable self-tests for ARMv7s page table allocator. This performs
63 a series of page-table consistency checks during boot.
65 If unsure, say N here.
67 config IOMMU_IO_PGTABLE_DART
68 bool "Apple DART Formats"
69 select IOMMU_IO_PGTABLE
70 depends on ARM64 || COMPILE_TEST
71 depends on !GENERIC_ATOMIC64 # for cmpxchg64()
73 Enable support for the Apple DART pagetable formats. These include
74 the t8020 and t6000/t8110 DART formats used in Apple M1/M2 family
77 If unsure, say N here.
82 bool "Export IOMMU internals in DebugFS"
85 Allows exposure of IOMMU device internals. This option enables
86 the use of debugfs by IOMMU drivers as required. Devices can,
87 at initialization time, cause the IOMMU code to create a top-level
88 debug/iommu directory, and then populate a subdirectory with
92 prompt "IOMMU default domain type"
94 default IOMMU_DEFAULT_DMA_LAZY if X86 || IA64
95 default IOMMU_DEFAULT_DMA_STRICT
97 Choose the type of IOMMU domain used to manage DMA API usage by
98 device drivers. The options here typically represent different
99 levels of tradeoff between robustness/security and performance,
100 depending on the IOMMU driver. Not all IOMMUs support all options.
101 This choice can be overridden at boot via the command line, and for
102 some devices also at runtime via sysfs.
104 If unsure, keep the default.
106 config IOMMU_DEFAULT_DMA_STRICT
107 bool "Translated - Strict"
109 Trusted devices use translation to restrict their access to only
110 DMA-mapped pages, with strict TLB invalidation on unmap. Equivalent
111 to passing "iommu.passthrough=0 iommu.strict=1" on the command line.
113 Untrusted devices always use this mode, with an additional layer of
114 bounce-buffering such that they cannot gain access to any unrelated
115 data within a mapped page.
117 config IOMMU_DEFAULT_DMA_LAZY
118 bool "Translated - Lazy"
120 Trusted devices use translation to restrict their access to only
121 DMA-mapped pages, but with "lazy" batched TLB invalidation. This
122 mode allows higher performance with some IOMMUs due to reduced TLB
123 flushing, but at the cost of reduced isolation since devices may be
124 able to access memory for some time after it has been unmapped.
125 Equivalent to passing "iommu.passthrough=0 iommu.strict=0" on the
128 If this mode is not supported by the IOMMU driver, the effective
129 runtime default will fall back to IOMMU_DEFAULT_DMA_STRICT.
131 config IOMMU_DEFAULT_PASSTHROUGH
134 Trusted devices are identity-mapped, giving them unrestricted access
135 to memory with minimal performance overhead. Equivalent to passing
136 "iommu.passthrough=1" (historically "iommu=pt") on the command line.
138 If this mode is not supported by the IOMMU driver, the effective
139 runtime default will fall back to IOMMU_DEFAULT_DMA_STRICT.
145 depends on OF && IOMMU_API
147 # IOMMU-agnostic DMA-mapping layer
149 def_bool ARM64 || IA64 || X86
154 select NEED_SG_DMA_LENGTH
156 # Shared Virtual Addressing
161 bool "Freescale IOMMU support"
163 depends on PHYS_64BIT
164 depends on PPC_E500MC || (COMPILE_TEST && PPC)
166 select GENERIC_ALLOCATOR
168 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
169 PAMU can authorize memory access, remap the memory address, and remap I/O
174 bool "MSM IOMMU Support"
176 depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST
178 select IOMMU_IO_PGTABLE_ARMV7S
180 Support for the IOMMUs found on certain Qualcomm SOCs.
181 These IOMMUs allow virtualization of the address space used by most
182 cores within the multimedia subsystem.
184 If unsure, say N here.
186 source "drivers/iommu/amd/Kconfig"
187 source "drivers/iommu/intel/Kconfig"
188 source "drivers/iommu/iommufd/Kconfig"
191 bool "Support for Interrupt Remapping"
192 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
195 Supports Interrupt remapping for IO-APIC and MSI devices.
196 To use x2apic mode in the CPU's which support x2APIC enhancements or
197 to support platforms with CPU's having > 8 bit APIC ID, say Y.
201 bool "OMAP IOMMU Support"
202 depends on ARCH_OMAP2PLUS || COMPILE_TEST
205 The OMAP3 media platform drivers depend on iommu support,
206 if you need them say Y here.
208 config OMAP_IOMMU_DEBUG
209 bool "Export OMAP IOMMU internals in DebugFS"
210 depends on OMAP_IOMMU && DEBUG_FS
212 Select this to see extensive information about
213 the internal state of OMAP IOMMU in debugfs.
215 Say N unless you know you need this.
217 config ROCKCHIP_IOMMU
218 bool "Rockchip IOMMU Support"
219 depends on ARCH_ROCKCHIP || COMPILE_TEST
221 select ARM_DMA_USE_IOMMU
223 Support for IOMMUs found on Rockchip rk32xx SOCs.
224 These IOMMUs allow virtualization of the address space used by most
225 cores within the multimedia subsystem.
226 Say Y here if you are using a Rockchip SoC that includes an IOMMU
230 bool "Allwinner H6 IOMMU Support"
232 depends on ARCH_SUNXI || COMPILE_TEST
233 select ARM_DMA_USE_IOMMU
236 Support for the IOMMU introduced in the Allwinner H6 SoCs.
238 config TEGRA_IOMMU_GART
239 bool "Tegra GART IOMMU Support"
240 depends on ARCH_TEGRA_2x_SOC
244 Enables support for remapping discontiguous physical memory
245 shared with the operating system into contiguous I/O virtual
246 space through the GART (Graphics Address Relocation Table)
247 hardware included on Tegra SoCs.
249 config TEGRA_IOMMU_SMMU
250 bool "NVIDIA Tegra SMMU Support"
251 depends on ARCH_TEGRA
256 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
257 SoCs (Tegra30 up to Tegra210).
260 bool "Exynos IOMMU Support"
261 depends on ARCH_EXYNOS || COMPILE_TEST
262 depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes
264 select ARM_DMA_USE_IOMMU
266 Support for the IOMMU (System MMU) of Samsung Exynos application
267 processor family. This enables H/W multimedia accelerators to see
268 non-linear physical memory chunks as linear memory in their
271 If unsure, say N here.
273 config EXYNOS_IOMMU_DEBUG
274 bool "Debugging log for Exynos IOMMU"
275 depends on EXYNOS_IOMMU
277 Select this to see the detailed log message that shows what
278 happens in the IOMMU driver.
280 Say N unless you need kernel log message for IOMMU debugging.
283 bool "Renesas VMSA-compatible IPMMU"
284 depends on ARCH_RENESAS || COMPILE_TEST
285 depends on ARM || ARM64 || COMPILE_TEST
286 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
288 select IOMMU_IO_PGTABLE_LPAE
289 select ARM_DMA_USE_IOMMU
291 Support for the Renesas VMSA-compatible IPMMU found in the R-Mobile
292 APE6, R-Car Gen{2,3} and RZ/G{1,2} SoCs.
296 config SPAPR_TCE_IOMMU
297 bool "sPAPR TCE IOMMU Support"
298 depends on PPC_POWERNV || PPC_PSERIES
301 Enables bits of IOMMU API required by VFIO. The iommu_ops
302 is not implemented as it is not necessary for VFIO.
305 tristate "Apple DART IOMMU Support"
306 depends on ARCH_APPLE || COMPILE_TEST
307 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_DART
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
323 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
325 select IOMMU_IO_PGTABLE_LPAE
326 select ARM_DMA_USE_IOMMU if ARM
328 Support for implementations of the ARM System MMU architecture
331 Say Y here if your SoC includes an IOMMU device implementing
332 the ARM SMMU architecture.
334 config ARM_SMMU_LEGACY_DT_BINDINGS
335 bool "Support the legacy \"mmu-masters\" devicetree bindings"
336 depends on ARM_SMMU=y && OF
338 Support for the badly designed and deprecated "mmu-masters"
339 devicetree bindings. This allows some DMA masters to attach
340 to the SMMU but does not provide any support via the DMA API.
341 If you're lucky, you might be able to get VFIO up and running.
343 If you say Y here then you'll make me very sad. Instead, say N
344 and move your firmware to the utopian future that was 2016.
346 config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT
347 bool "Default to disabling bypass on ARM SMMU v1 and v2"
351 Say Y here to (by default) disable bypass streams such that
352 incoming transactions from devices that are not attached to
353 an iommu domain will report an abort back to the device and
354 will not be allowed to pass through the SMMU.
356 Any old kernels that existed before this KConfig was
357 introduced would default to _allowing_ bypass (AKA the
358 equivalent of NO for this config). However the default for
359 this option is YES because the old behavior is insecure.
361 There are few reasons to allow unmatched stream bypass, and
362 even fewer good ones. If saying YES here breaks your board
363 you should work on fixing your board. This KConfig option
364 is expected to be removed in the future and we'll simply
365 hardcode the bypass disable in the code.
367 NOTE: the kernel command line parameter
368 'arm-smmu.disable_bypass' will continue to override this
373 depends on ARM_SMMU && ARCH_QCOM
376 When running on a Qualcomm platform that has the custom variant
377 of the ARM SMMU, this needs to be built into the SMMU driver.
379 config ARM_SMMU_QCOM_DEBUG
380 bool "ARM SMMU QCOM implementation defined debug support"
381 depends on ARM_SMMU_QCOM
383 Support for implementation specific debug features in ARM SMMU
384 hardware found in QTI platforms.
386 Say Y here to enable debug for issues such as TLB sync timeouts
387 which requires implementation defined register dumps.
390 tristate "ARM Ltd. System MMU Version 3 (SMMUv3) Support"
393 select IOMMU_IO_PGTABLE_LPAE
394 select GENERIC_MSI_IRQ
396 Support for implementations of the ARM System MMU architecture
397 version 3 providing translation support to a PCIe root complex.
399 Say Y here if your system includes an IOMMU device implementing
400 the ARM SMMUv3 architecture.
402 config ARM_SMMU_V3_SVA
403 bool "Shared Virtual Addressing support for the ARM SMMUv3"
404 depends on ARM_SMMU_V3
408 Support for sharing process address spaces with devices using the
411 Say Y here if your system supports SVA extensions such as PCIe PASID
415 def_bool y if S390 && PCI
416 depends on S390 && PCI
419 Support for the IOMMU API for s390 PCI devices.
422 tristate "MediaTek IOMMU Support"
423 depends on ARCH_MEDIATEK || COMPILE_TEST
424 select ARM_DMA_USE_IOMMU
426 select IOMMU_IO_PGTABLE_ARMV7S
430 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia
431 Memory Management Unit. This option enables remapping of DMA memory
432 accesses for the multimedia subsystem.
434 If unsure, say N here.
437 tristate "MediaTek IOMMU Version 1 (M4U gen1) Support"
439 depends on ARCH_MEDIATEK || COMPILE_TEST
440 select ARM_DMA_USE_IOMMU
445 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is
446 Multimedia Memory Managememt Unit. This option enables remapping of
447 DMA memory accesses for the multimedia subsystem.
449 if unsure, say N here.
452 # Note: iommu drivers cannot (yet?) be built as modules
453 bool "Qualcomm IOMMU Support"
454 depends on ARCH_QCOM || COMPILE_TEST
455 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
458 select IOMMU_IO_PGTABLE_LPAE
459 select ARM_DMA_USE_IOMMU
461 Support for IOMMU on certain Qualcomm SoCs.
464 bool "Hyper-V IRQ Handling"
465 depends on HYPERV && X86
469 Stub IOMMU driver to handle IRQs to support Hyper-V Linux
470 guest and root partitions.
473 tristate "Virtio IOMMU driver"
475 depends on (ARM64 || X86)
478 select ACPI_VIOT if ACPI
480 Para-virtualised IOMMU driver with virtio.
482 Say Y here if you intend to run this kernel as a guest.
485 tristate "Unisoc IOMMU Support"
486 depends on ARCH_SPRD || COMPILE_TEST
489 Support for IOMMU on Unisoc's SoCs, this IOMMU can be used by
490 Unisoc's multimedia devices, such as display, Image codec(jpeg)
491 and a few signal processors, including VSP(video), GSP(graphic),
492 ISP(image), and CPP(camera pixel processor), etc.
494 Say Y here if you want to use the multimedia devices listed above.
496 endif # IOMMU_SUPPORT