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
155 select NEED_SG_DMA_FLAGS if SWIOTLB
157 # Shared Virtual Addressing
162 bool "Freescale IOMMU support"
164 depends on PHYS_64BIT
165 depends on PPC_E500MC || (COMPILE_TEST && PPC)
167 select GENERIC_ALLOCATOR
169 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
170 PAMU can authorize memory access, remap the memory address, and remap I/O
175 bool "MSM IOMMU Support"
177 depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST
179 select IOMMU_IO_PGTABLE_ARMV7S
181 Support for the IOMMUs found on certain Qualcomm SOCs.
182 These IOMMUs allow virtualization of the address space used by most
183 cores within the multimedia subsystem.
185 If unsure, say N here.
187 source "drivers/iommu/amd/Kconfig"
188 source "drivers/iommu/intel/Kconfig"
189 source "drivers/iommu/iommufd/Kconfig"
192 bool "Support for Interrupt Remapping"
193 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
196 Supports Interrupt remapping for IO-APIC and MSI devices.
197 To use x2apic mode in the CPU's which support x2APIC enhancements or
198 to support platforms with CPU's having > 8 bit APIC ID, say Y.
202 bool "OMAP IOMMU Support"
203 depends on ARCH_OMAP2PLUS || COMPILE_TEST
206 The OMAP3 media platform drivers depend on iommu support,
207 if you need them say Y here.
209 config OMAP_IOMMU_DEBUG
210 bool "Export OMAP IOMMU internals in DebugFS"
211 depends on OMAP_IOMMU && DEBUG_FS
213 Select this to see extensive information about
214 the internal state of OMAP IOMMU in debugfs.
216 Say N unless you know you need this.
218 config ROCKCHIP_IOMMU
219 bool "Rockchip IOMMU Support"
220 depends on ARCH_ROCKCHIP || COMPILE_TEST
222 select ARM_DMA_USE_IOMMU
224 Support for IOMMUs found on Rockchip rk32xx SOCs.
225 These IOMMUs allow virtualization of the address space used by most
226 cores within the multimedia subsystem.
227 Say Y here if you are using a Rockchip SoC that includes an IOMMU
231 bool "Allwinner H6 IOMMU Support"
233 depends on ARCH_SUNXI || COMPILE_TEST
234 select ARM_DMA_USE_IOMMU
237 Support for the IOMMU introduced in the Allwinner H6 SoCs.
239 config TEGRA_IOMMU_GART
240 bool "Tegra GART IOMMU Support"
241 depends on ARCH_TEGRA_2x_SOC
245 Enables support for remapping discontiguous physical memory
246 shared with the operating system into contiguous I/O virtual
247 space through the GART (Graphics Address Relocation Table)
248 hardware included on Tegra SoCs.
250 config TEGRA_IOMMU_SMMU
251 bool "NVIDIA Tegra SMMU Support"
252 depends on ARCH_TEGRA
257 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
258 SoCs (Tegra30 up to Tegra210).
261 bool "Exynos IOMMU Support"
262 depends on ARCH_EXYNOS || COMPILE_TEST
263 depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes
265 select ARM_DMA_USE_IOMMU
267 Support for the IOMMU (System MMU) of Samsung Exynos application
268 processor family. This enables H/W multimedia accelerators to see
269 non-linear physical memory chunks as linear memory in their
272 If unsure, say N here.
274 config EXYNOS_IOMMU_DEBUG
275 bool "Debugging log for Exynos IOMMU"
276 depends on EXYNOS_IOMMU
278 Select this to see the detailed log message that shows what
279 happens in the IOMMU driver.
281 Say N unless you need kernel log message for IOMMU debugging.
284 bool "Renesas VMSA-compatible IPMMU"
285 depends on ARCH_RENESAS || COMPILE_TEST
286 depends on ARM || ARM64 || COMPILE_TEST
287 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
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
308 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_DART
310 select IOMMU_IO_PGTABLE_DART
313 Support for Apple DART (Device Address Resolution Table) IOMMUs
314 found in Apple ARM SoCs like the M1.
315 This IOMMU is required for most peripherals using DMA to access
318 Say Y here if you are using an Apple SoC.
322 tristate "ARM Ltd. System MMU (SMMU) Support"
323 depends on ARM64 || ARM || COMPILE_TEST
324 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
326 select IOMMU_IO_PGTABLE_LPAE
327 select ARM_DMA_USE_IOMMU if ARM
329 Support for implementations of the ARM System MMU architecture
332 Say Y here if your SoC includes an IOMMU device implementing
333 the ARM SMMU architecture.
335 config ARM_SMMU_LEGACY_DT_BINDINGS
336 bool "Support the legacy \"mmu-masters\" devicetree bindings"
337 depends on ARM_SMMU=y && OF
339 Support for the badly designed and deprecated "mmu-masters"
340 devicetree bindings. This allows some DMA masters to attach
341 to the SMMU but does not provide any support via the DMA API.
342 If you're lucky, you might be able to get VFIO up and running.
344 If you say Y here then you'll make me very sad. Instead, say N
345 and move your firmware to the utopian future that was 2016.
347 config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT
348 bool "Default to disabling bypass on ARM SMMU v1 and v2"
352 Say Y here to (by default) disable bypass streams such that
353 incoming transactions from devices that are not attached to
354 an iommu domain will report an abort back to the device and
355 will not be allowed to pass through the SMMU.
357 Any old kernels that existed before this KConfig was
358 introduced would default to _allowing_ bypass (AKA the
359 equivalent of NO for this config). However the default for
360 this option is YES because the old behavior is insecure.
362 There are few reasons to allow unmatched stream bypass, and
363 even fewer good ones. If saying YES here breaks your board
364 you should work on fixing your board. This KConfig option
365 is expected to be removed in the future and we'll simply
366 hardcode the bypass disable in the code.
368 NOTE: the kernel command line parameter
369 'arm-smmu.disable_bypass' will continue to override this
374 depends on ARM_SMMU && ARCH_QCOM
377 When running on a Qualcomm platform that has the custom variant
378 of the ARM SMMU, this needs to be built into the SMMU driver.
380 config ARM_SMMU_QCOM_DEBUG
381 bool "ARM SMMU QCOM implementation defined debug support"
382 depends on ARM_SMMU_QCOM
384 Support for implementation specific debug features in ARM SMMU
385 hardware found in QTI platforms.
387 Say Y here to enable debug for issues such as TLB sync timeouts
388 which requires implementation defined register dumps.
391 tristate "ARM Ltd. System MMU Version 3 (SMMUv3) Support"
394 select IOMMU_IO_PGTABLE_LPAE
395 select GENERIC_MSI_IRQ
397 Support for implementations of the ARM System MMU architecture
398 version 3 providing translation support to a PCIe root complex.
400 Say Y here if your system includes an IOMMU device implementing
401 the ARM SMMUv3 architecture.
403 config ARM_SMMU_V3_SVA
404 bool "Shared Virtual Addressing support for the ARM SMMUv3"
405 depends on ARM_SMMU_V3
409 Support for sharing process address spaces with devices using the
412 Say Y here if your system supports SVA extensions such as PCIe PASID
416 def_bool y if S390 && PCI
417 depends on S390 && PCI
420 Support for the IOMMU API for s390 PCI devices.
423 tristate "MediaTek IOMMU Support"
424 depends on ARCH_MEDIATEK || COMPILE_TEST
425 select ARM_DMA_USE_IOMMU
427 select IOMMU_IO_PGTABLE_ARMV7S
431 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia
432 Memory Management Unit. This option enables remapping of DMA memory
433 accesses for the multimedia subsystem.
435 If unsure, say N here.
438 tristate "MediaTek IOMMU Version 1 (M4U gen1) Support"
440 depends on ARCH_MEDIATEK || COMPILE_TEST
441 select ARM_DMA_USE_IOMMU
446 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is
447 Multimedia Memory Managememt Unit. This option enables remapping of
448 DMA memory accesses for the multimedia subsystem.
450 if unsure, say N here.
453 # Note: iommu drivers cannot (yet?) be built as modules
454 bool "Qualcomm IOMMU Support"
455 depends on ARCH_QCOM || COMPILE_TEST
456 depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
459 select IOMMU_IO_PGTABLE_LPAE
460 select ARM_DMA_USE_IOMMU
462 Support for IOMMU on certain Qualcomm SoCs.
465 bool "Hyper-V IRQ Handling"
466 depends on HYPERV && X86
470 Stub IOMMU driver to handle IRQs to support Hyper-V Linux
471 guest and root partitions.
474 tristate "Virtio IOMMU driver"
476 depends on (ARM64 || X86)
479 select ACPI_VIOT if ACPI
481 Para-virtualised IOMMU driver with virtio.
483 Say Y here if you intend to run this kernel as a guest.
486 tristate "Unisoc IOMMU Support"
487 depends on ARCH_SPRD || COMPILE_TEST
490 Support for IOMMU on Unisoc's SoCs, this IOMMU can be used by
491 Unisoc's multimedia devices, such as display, Image codec(jpeg)
492 and a few signal processors, including VSP(video), GSP(graphic),
493 ISP(image), and CPP(camera pixel processor), etc.
495 Say Y here if you want to use the multimedia devices listed above.
497 endif # IOMMU_SUPPORT