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
166 bool "Freescale IOMMU support"
168 depends on PHYS_64BIT
169 depends on PPC_E500MC || (COMPILE_TEST && PPC)
171 select GENERIC_ALLOCATOR
173 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
174 PAMU can authorize memory access, remap the memory address, and remap I/O
179 bool "MSM IOMMU Support"
181 depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST
183 select IOMMU_IO_PGTABLE_ARMV7S
185 Support for the IOMMUs found on certain Qualcomm SOCs.
186 These IOMMUs allow virtualization of the address space used by most
187 cores within the multimedia subsystem.
189 If unsure, say N here.
191 source "drivers/iommu/amd/Kconfig"
192 source "drivers/iommu/intel/Kconfig"
193 source "drivers/iommu/iommufd/Kconfig"
196 bool "Support for Interrupt Remapping"
197 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
200 Supports Interrupt remapping for IO-APIC and MSI devices.
201 To use x2apic mode in the CPU's which support x2APIC enhancements or
202 to support platforms with CPU's having > 8 bit APIC ID, say Y.
206 bool "OMAP IOMMU Support"
207 depends on ARCH_OMAP2PLUS || COMPILE_TEST
210 The OMAP3 media platform drivers depend on iommu support,
211 if you need them say Y here.
213 config OMAP_IOMMU_DEBUG
214 bool "Export OMAP IOMMU internals in DebugFS"
215 depends on OMAP_IOMMU && DEBUG_FS
217 Select this to see extensive information about
218 the internal state of OMAP IOMMU in debugfs.
220 Say N unless you know you need this.
222 config ROCKCHIP_IOMMU
223 bool "Rockchip IOMMU Support"
224 depends on ARCH_ROCKCHIP || COMPILE_TEST
226 select ARM_DMA_USE_IOMMU
228 Support for IOMMUs found on Rockchip rk32xx SOCs.
229 These IOMMUs allow virtualization of the address space used by most
230 cores within the multimedia subsystem.
231 Say Y here if you are using a Rockchip SoC that includes an IOMMU
235 bool "Allwinner H6 IOMMU Support"
237 depends on ARCH_SUNXI || COMPILE_TEST
238 select ARM_DMA_USE_IOMMU
241 Support for the IOMMU introduced in the Allwinner H6 SoCs.
243 config TEGRA_IOMMU_SMMU
244 bool "NVIDIA Tegra SMMU Support"
245 depends on ARCH_TEGRA
250 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
251 SoCs (Tegra30 up to Tegra210).
254 bool "Exynos IOMMU Support"
255 depends on ARCH_EXYNOS || COMPILE_TEST
256 depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes
258 select ARM_DMA_USE_IOMMU
260 Support for the IOMMU (System MMU) of Samsung Exynos application
261 processor family. This enables H/W multimedia accelerators to see
262 non-linear physical memory chunks as linear memory in their
265 If unsure, say N here.
267 config EXYNOS_IOMMU_DEBUG
268 bool "Debugging log for Exynos IOMMU"
269 depends on EXYNOS_IOMMU
271 Select this to see the detailed log message that shows what
272 happens in the IOMMU driver.
274 Say N unless you need kernel log message for IOMMU debugging.
277 bool "Renesas VMSA-compatible IPMMU"
278 depends on ARCH_RENESAS || COMPILE_TEST
279 depends on ARM || ARM64 || COMPILE_TEST
280 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
282 select IOMMU_IO_PGTABLE_LPAE
283 select ARM_DMA_USE_IOMMU
285 Support for the Renesas VMSA-compatible IPMMU found in the R-Mobile
286 APE6, R-Car Gen{2,3} and RZ/G{1,2} SoCs.
290 config SPAPR_TCE_IOMMU
291 bool "sPAPR TCE IOMMU Support"
292 depends on PPC_POWERNV || PPC_PSERIES
295 Enables bits of IOMMU API required by VFIO. The iommu_ops
296 is not implemented as it is not necessary for VFIO.
299 tristate "Apple DART IOMMU Support"
300 depends on ARCH_APPLE || COMPILE_TEST
301 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_DART
303 select IOMMU_IO_PGTABLE_DART
306 Support for Apple DART (Device Address Resolution Table) IOMMUs
307 found in Apple ARM SoCs like the M1.
308 This IOMMU is required for most peripherals using DMA to access
311 Say Y here if you are using an Apple SoC.
315 tristate "ARM Ltd. System MMU (SMMU) Support"
316 depends on ARM64 || ARM || COMPILE_TEST
317 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
319 select IOMMU_IO_PGTABLE_LPAE
320 select ARM_DMA_USE_IOMMU if ARM
322 Support for implementations of the ARM System MMU architecture
325 Say Y here if your SoC includes an IOMMU device implementing
326 the ARM SMMU architecture.
328 config ARM_SMMU_LEGACY_DT_BINDINGS
329 bool "Support the legacy \"mmu-masters\" devicetree bindings"
330 depends on ARM_SMMU=y && OF
332 Support for the badly designed and deprecated "mmu-masters"
333 devicetree bindings. This allows some DMA masters to attach
334 to the SMMU but does not provide any support via the DMA API.
335 If you're lucky, you might be able to get VFIO up and running.
337 If you say Y here then you'll make me very sad. Instead, say N
338 and move your firmware to the utopian future that was 2016.
340 config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT
341 bool "Default to disabling bypass on ARM SMMU v1 and v2"
345 Say Y here to (by default) disable bypass streams such that
346 incoming transactions from devices that are not attached to
347 an iommu domain will report an abort back to the device and
348 will not be allowed to pass through the SMMU.
350 Any old kernels that existed before this KConfig was
351 introduced would default to _allowing_ bypass (AKA the
352 equivalent of NO for this config). However the default for
353 this option is YES because the old behavior is insecure.
355 There are few reasons to allow unmatched stream bypass, and
356 even fewer good ones. If saying YES here breaks your board
357 you should work on fixing your board. This KConfig option
358 is expected to be removed in the future and we'll simply
359 hardcode the bypass disable in the code.
361 NOTE: the kernel command line parameter
362 'arm-smmu.disable_bypass' will continue to override this
367 depends on ARM_SMMU && ARCH_QCOM
370 When running on a Qualcomm platform that has the custom variant
371 of the ARM SMMU, this needs to be built into the SMMU driver.
373 config ARM_SMMU_QCOM_DEBUG
374 bool "ARM SMMU QCOM implementation defined debug support"
375 depends on ARM_SMMU_QCOM
377 Support for implementation specific debug features in ARM SMMU
378 hardware found in QTI platforms.
380 Say Y here to enable debug for issues such as TLB sync timeouts
381 which requires implementation defined register dumps.
384 tristate "ARM Ltd. System MMU Version 3 (SMMUv3) Support"
387 select IOMMU_IO_PGTABLE_LPAE
388 select GENERIC_MSI_IRQ
390 Support for implementations of the ARM System MMU architecture
391 version 3 providing translation support to a PCIe root complex.
393 Say Y here if your system includes an IOMMU device implementing
394 the ARM SMMUv3 architecture.
396 config ARM_SMMU_V3_SVA
397 bool "Shared Virtual Addressing support for the ARM SMMUv3"
398 depends on ARM_SMMU_V3
402 Support for sharing process address spaces with devices using the
405 Say Y here if your system supports SVA extensions such as PCIe PASID
409 def_bool y if S390 && PCI
410 depends on S390 && PCI
413 Support for the IOMMU API for s390 PCI devices.
416 tristate "MediaTek IOMMU Support"
417 depends on ARCH_MEDIATEK || COMPILE_TEST
418 select ARM_DMA_USE_IOMMU
420 select IOMMU_IO_PGTABLE_ARMV7S
424 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia
425 Memory Management Unit. This option enables remapping of DMA memory
426 accesses for the multimedia subsystem.
428 If unsure, say N here.
431 tristate "MediaTek IOMMU Version 1 (M4U gen1) Support"
433 depends on ARCH_MEDIATEK || COMPILE_TEST
434 select ARM_DMA_USE_IOMMU
439 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is
440 Multimedia Memory Managememt Unit. This option enables remapping of
441 DMA memory accesses for the multimedia subsystem.
443 if unsure, say N here.
446 # Note: iommu drivers cannot (yet?) be built as modules
447 bool "Qualcomm IOMMU Support"
448 depends on ARCH_QCOM || COMPILE_TEST
449 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
452 select IOMMU_IO_PGTABLE_LPAE
453 select ARM_DMA_USE_IOMMU
455 Support for IOMMU on certain Qualcomm SoCs.
458 bool "Hyper-V IRQ Handling"
459 depends on HYPERV && X86
463 Stub IOMMU driver to handle IRQs to support Hyper-V Linux
464 guest and root partitions.
467 tristate "Virtio IOMMU driver"
469 depends on (ARM64 || X86)
472 select ACPI_VIOT if ACPI
474 Para-virtualised IOMMU driver with virtio.
476 Say Y here if you intend to run this kernel as a guest.
479 tristate "Unisoc IOMMU Support"
480 depends on ARCH_SPRD || COMPILE_TEST
483 Support for IOMMU on Unisoc's SoCs, this IOMMU can be used by
484 Unisoc's multimedia devices, such as display, Image codec(jpeg)
485 and a few signal processors, including VSP(video), GSP(graphic),
486 ISP(image), and CPP(camera pixel processor), etc.
488 Say Y here if you want to use the multimedia devices listed above.
490 endif # IOMMU_SUPPORT