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"
193 bool "Support for Interrupt Remapping"
194 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
197 Supports Interrupt remapping for IO-APIC and MSI devices.
198 To use x2apic mode in the CPU's which support x2APIC enhancements or
199 to support platforms with CPU's having > 8 bit APIC ID, say Y.
203 bool "OMAP IOMMU Support"
204 depends on ARCH_OMAP2PLUS || COMPILE_TEST
207 The OMAP3 media platform drivers depend on iommu support,
208 if you need them say Y here.
210 config OMAP_IOMMU_DEBUG
211 bool "Export OMAP IOMMU internals in DebugFS"
212 depends on OMAP_IOMMU && DEBUG_FS
214 Select this to see extensive information about
215 the internal state of OMAP IOMMU in debugfs.
217 Say N unless you know you need this.
219 config ROCKCHIP_IOMMU
220 bool "Rockchip IOMMU Support"
221 depends on ARCH_ROCKCHIP || COMPILE_TEST
223 select ARM_DMA_USE_IOMMU
225 Support for IOMMUs found on Rockchip rk32xx SOCs.
226 These IOMMUs allow virtualization of the address space used by most
227 cores within the multimedia subsystem.
228 Say Y here if you are using a Rockchip SoC that includes an IOMMU
232 bool "Allwinner H6 IOMMU Support"
234 depends on ARCH_SUNXI || COMPILE_TEST
235 select ARM_DMA_USE_IOMMU
238 Support for the IOMMU introduced in the Allwinner H6 SoCs.
240 config TEGRA_IOMMU_GART
241 bool "Tegra GART IOMMU Support"
242 depends on ARCH_TEGRA_2x_SOC
246 Enables support for remapping discontiguous physical memory
247 shared with the operating system into contiguous I/O virtual
248 space through the GART (Graphics Address Relocation Table)
249 hardware included on Tegra SoCs.
251 config TEGRA_IOMMU_SMMU
252 bool "NVIDIA Tegra SMMU Support"
253 depends on ARCH_TEGRA
258 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
259 SoCs (Tegra30 up to Tegra210).
262 bool "Exynos IOMMU Support"
263 depends on ARCH_EXYNOS || COMPILE_TEST
264 depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes
266 select ARM_DMA_USE_IOMMU
268 Support for the IOMMU (System MMU) of Samsung Exynos application
269 processor family. This enables H/W multimedia accelerators to see
270 non-linear physical memory chunks as linear memory in their
273 If unsure, say N here.
275 config EXYNOS_IOMMU_DEBUG
276 bool "Debugging log for Exynos IOMMU"
277 depends on EXYNOS_IOMMU
279 Select this to see the detailed log message that shows what
280 happens in the IOMMU driver.
282 Say N unless you need kernel log message for IOMMU debugging.
285 bool "Renesas VMSA-compatible IPMMU"
286 depends on ARCH_RENESAS || (COMPILE_TEST && !GENERIC_ATOMIC64)
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 && !GENERIC_ATOMIC64)
308 select IOMMU_IO_PGTABLE_DART
311 Support for Apple DART (Device Address Resolution Table) IOMMUs
312 found in Apple ARM SoCs like the M1.
313 This IOMMU is required for most peripherals using DMA to access
316 Say Y here if you are using an Apple SoC.
320 tristate "ARM Ltd. System MMU (SMMU) Support"
321 depends on ARM64 || ARM || (COMPILE_TEST && !GENERIC_ATOMIC64)
323 select IOMMU_IO_PGTABLE_LPAE
324 select ARM_DMA_USE_IOMMU if ARM
326 Support for implementations of the ARM System MMU architecture
329 Say Y here if your SoC includes an IOMMU device implementing
330 the ARM SMMU architecture.
332 config ARM_SMMU_LEGACY_DT_BINDINGS
333 bool "Support the legacy \"mmu-masters\" devicetree bindings"
334 depends on ARM_SMMU=y && OF
336 Support for the badly designed and deprecated "mmu-masters"
337 devicetree bindings. This allows some DMA masters to attach
338 to the SMMU but does not provide any support via the DMA API.
339 If you're lucky, you might be able to get VFIO up and running.
341 If you say Y here then you'll make me very sad. Instead, say N
342 and move your firmware to the utopian future that was 2016.
344 config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT
345 bool "Default to disabling bypass on ARM SMMU v1 and v2"
349 Say Y here to (by default) disable bypass streams such that
350 incoming transactions from devices that are not attached to
351 an iommu domain will report an abort back to the device and
352 will not be allowed to pass through the SMMU.
354 Any old kernels that existed before this KConfig was
355 introduced would default to _allowing_ bypass (AKA the
356 equivalent of NO for this config). However the default for
357 this option is YES because the old behavior is insecure.
359 There are few reasons to allow unmatched stream bypass, and
360 even fewer good ones. If saying YES here breaks your board
361 you should work on fixing your board. This KConfig option
362 is expected to be removed in the future and we'll simply
363 hardcode the bypass disable in the code.
365 NOTE: the kernel command line parameter
366 'arm-smmu.disable_bypass' will continue to override this
371 depends on ARM_SMMU && ARCH_QCOM
374 When running on a Qualcomm platform that has the custom variant
375 of the ARM SMMU, this needs to be built into the SMMU driver.
377 config ARM_SMMU_QCOM_DEBUG
378 bool "ARM SMMU QCOM implementation defined debug support"
379 depends on ARM_SMMU_QCOM
381 Support for implementation specific debug features in ARM SMMU
382 hardware found in QTI platforms.
384 Say Y here to enable debug for issues such as TLB sync timeouts
385 which requires implementation defined register dumps.
388 tristate "ARM Ltd. System MMU Version 3 (SMMUv3) Support"
391 select IOMMU_IO_PGTABLE_LPAE
392 select GENERIC_MSI_IRQ_DOMAIN
394 Support for implementations of the ARM System MMU architecture
395 version 3 providing translation support to a PCIe root complex.
397 Say Y here if your system includes an IOMMU device implementing
398 the ARM SMMUv3 architecture.
400 config ARM_SMMU_V3_SVA
401 bool "Shared Virtual Addressing support for the ARM SMMUv3"
402 depends on ARM_SMMU_V3
406 Support for sharing process address spaces with devices using the
409 Say Y here if your system supports SVA extensions such as PCIe PASID
413 def_bool y if S390 && PCI
414 depends on S390 && PCI
417 Support for the IOMMU API for s390 PCI devices.
419 config S390_CCW_IOMMU
420 bool "S390 CCW IOMMU Support"
421 depends on S390 && CCW || COMPILE_TEST
424 Enables bits of IOMMU API required by VFIO. The iommu_ops
425 is not implemented as it is not necessary for VFIO.
428 bool "S390 AP IOMMU Support"
429 depends on S390 && ZCRYPT || COMPILE_TEST
432 Enables bits of IOMMU API required by VFIO. The iommu_ops
433 is not implemented as it is not necessary for VFIO.
436 tristate "MediaTek IOMMU Support"
437 depends on ARCH_MEDIATEK || COMPILE_TEST
438 select ARM_DMA_USE_IOMMU
440 select IOMMU_IO_PGTABLE_ARMV7S
444 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia
445 Memory Management Unit. This option enables remapping of DMA memory
446 accesses for the multimedia subsystem.
448 If unsure, say N here.
451 tristate "MediaTek IOMMU Version 1 (M4U gen1) Support"
453 depends on ARCH_MEDIATEK || COMPILE_TEST
454 select ARM_DMA_USE_IOMMU
459 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is
460 Multimedia Memory Managememt Unit. This option enables remapping of
461 DMA memory accesses for the multimedia subsystem.
463 if unsure, say N here.
466 # Note: iommu drivers cannot (yet?) be built as modules
467 bool "Qualcomm IOMMU Support"
468 depends on ARCH_QCOM || (COMPILE_TEST && !GENERIC_ATOMIC64)
471 select IOMMU_IO_PGTABLE_LPAE
472 select ARM_DMA_USE_IOMMU
474 Support for IOMMU on certain Qualcomm SoCs.
477 bool "Hyper-V x2APIC IRQ Handling"
478 depends on HYPERV && X86
482 Stub IOMMU driver to handle IRQs as to allow Hyper-V Linux
483 guests to run with x2APIC mode enabled.
486 tristate "Virtio IOMMU driver"
488 depends on (ARM64 || X86)
491 select ACPI_VIOT if ACPI
493 Para-virtualised IOMMU driver with virtio.
495 Say Y here if you intend to run this kernel as a guest.
498 tristate "Unisoc IOMMU Support"
499 depends on ARCH_SPRD || COMPILE_TEST
502 Support for IOMMU on Unisoc's SoCs, this IOMMU can be used by
503 Unisoc's multimedia devices, such as display, Image codec(jpeg)
504 and a few signal processors, including VSP(video), GSP(graphic),
505 ISP(image), and CPP(camera pixel processor), etc.
507 Say Y here if you want to use the multimedia devices listed above.
509 endif # IOMMU_SUPPORT