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.
73 bool "Export IOMMU internals in DebugFS"
76 Allows exposure of IOMMU device internals. This option enables
77 the use of debugfs by IOMMU drivers as required. Devices can,
78 at initialization time, cause the IOMMU code to create a top-level
79 debug/iommu directory, and then populate a subdirectory with
82 config IOMMU_DEFAULT_PASSTHROUGH
83 bool "IOMMU passthrough by default"
86 Enable passthrough by default, removing the need to pass in
87 iommu.passthrough=on or iommu=pt through command line. If this
88 is enabled, you can still disable with iommu.passthrough=off
89 or iommu=nopt depending on the architecture.
91 If unsure, say N here.
95 depends on OF && IOMMU_API
97 # IOMMU-agnostic DMA-mapping layer
103 select NEED_SG_DMA_LENGTH
106 bool "Freescale IOMMU support"
108 depends on PHYS_64BIT
109 depends on PPC_E500MC || (COMPILE_TEST && PPC)
111 select GENERIC_ALLOCATOR
113 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
114 PAMU can authorize memory access, remap the memory address, and remap I/O
119 bool "MSM IOMMU Support"
121 depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST
123 select IOMMU_IO_PGTABLE_ARMV7S
125 Support for the IOMMUs found on certain Qualcomm SOCs.
126 These IOMMUs allow virtualization of the address space used by most
127 cores within the multimedia subsystem.
129 If unsure, say N here.
131 config IOMMU_PGTABLES_L2
133 depends on MSM_IOMMU && MMU && SMP && CPU_DCACHE_DISABLE=n
137 bool "AMD IOMMU support"
146 depends on X86_64 && PCI && ACPI
148 With this option you can enable support for AMD IOMMU hardware in
149 your system. An IOMMU is a hardware component which provides
150 remapping of DMA memory accesses from devices. With an AMD IOMMU you
151 can isolate the DMA memory of different devices and protect the
152 system from misbehaving device drivers or hardware.
154 You can find out if your system has an AMD IOMMU if you look into
155 your BIOS for an option to enable it or if you have an IVRS ACPI
159 tristate "AMD IOMMU Version 2 driver"
163 This option enables support for the AMD IOMMUv2 features of the IOMMU
164 hardware. Select this option if you want to use devices that support
165 the PCI PRI and PASID interface.
167 config AMD_IOMMU_DEBUGFS
168 bool "Enable AMD IOMMU internals in DebugFS"
169 depends on AMD_IOMMU && IOMMU_DEBUGFS
171 !!!WARNING!!! !!!WARNING!!! !!!WARNING!!! !!!WARNING!!!
173 DO NOT ENABLE THIS OPTION UNLESS YOU REALLY, -REALLY- KNOW WHAT YOU ARE DOING!!!
174 Exposes AMD IOMMU device internals in DebugFS.
176 This option is -NOT- intended for production environments, and should
177 not generally be enabled.
179 # Intel IOMMU support
184 bool "Support for Intel IOMMU using DMA Remapping Devices"
185 depends on PCI_MSI && ACPI && (X86 || IA64)
188 select NEED_DMA_MAP_STATE
192 DMA remapping (DMAR) devices support enables independent address
193 translations for Direct Memory Access (DMA) from devices.
194 These DMA remapping devices are reported via ACPI tables
195 and include PCI device scope covered by these DMA
198 config INTEL_IOMMU_DEBUGFS
199 bool "Export Intel IOMMU internals in Debugfs"
200 depends on INTEL_IOMMU && IOMMU_DEBUGFS
204 DO NOT ENABLE THIS OPTION UNLESS YOU REALLY KNOW WHAT YOU ARE DOING!!!
206 Expose Intel IOMMU internals in Debugfs.
208 This option is -NOT- intended for production environments, and should
209 only be enabled for debugging Intel IOMMU.
211 config INTEL_IOMMU_SVM
212 bool "Support for Shared Virtual Memory with Intel IOMMU"
213 depends on INTEL_IOMMU && X86
218 Shared Virtual Memory (SVM) provides a facility for devices
219 to access DMA resources through process address space by
220 means of a Process Address Space ID (PASID).
222 config INTEL_IOMMU_DEFAULT_ON
224 prompt "Enable Intel DMA Remapping Devices by default"
225 depends on INTEL_IOMMU
227 Selecting this option will enable a DMAR device at boot time if
228 one is found. If this option is not selected, DMAR support can
229 be enabled by passing intel_iommu=on to the kernel.
231 config INTEL_IOMMU_BROKEN_GFX_WA
232 bool "Workaround broken graphics drivers (going away soon)"
233 depends on INTEL_IOMMU && BROKEN && X86
235 Current Graphics drivers tend to use physical address
236 for DMA and avoid using DMA APIs. Setting this config
237 option permits the IOMMU driver to set a unity map for
238 all the OS-visible memory. Hence the driver can continue
239 to use physical addresses for DMA, at least until this
240 option is removed in the 2.6.32 kernel.
242 config INTEL_IOMMU_FLOPPY_WA
244 depends on INTEL_IOMMU && X86
246 Floppy disk drivers are known to bypass DMA API calls
247 thereby failing to work when IOMMU is enabled. This
248 workaround will setup a 1:1 mapping for the first
249 16MiB to make floppy (an ISA device) work.
251 config INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON
252 bool "Enable Intel IOMMU scalable mode by default"
253 depends on INTEL_IOMMU
255 Selecting this option will enable by default the scalable mode if
256 hardware presents the capability. The scalable mode is defined in
257 VT-d 3.0. The scalable mode capability could be checked by reading
258 /sys/devices/virtual/iommu/dmar*/intel-iommu/ecap. If this option
259 is not selected, scalable mode support could also be enabled by
260 passing intel_iommu=sm_on to the kernel. If not sure, please use
264 bool "Support for Interrupt Remapping"
265 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
268 Supports Interrupt remapping for IO-APIC and MSI devices.
269 To use x2apic mode in the CPU's which support x2APIC enhancements or
270 to support platforms with CPU's having > 8 bit APIC ID, say Y.
274 bool "OMAP IOMMU Support"
275 depends on ARM && MMU
276 depends on ARCH_OMAP2PLUS || COMPILE_TEST
279 The OMAP3 media platform drivers depend on iommu support,
280 if you need them say Y here.
282 config OMAP_IOMMU_DEBUG
283 bool "Export OMAP IOMMU internals in DebugFS"
284 depends on OMAP_IOMMU && DEBUG_FS
286 Select this to see extensive information about
287 the internal state of OMAP IOMMU in debugfs.
289 Say N unless you know you need this.
291 config ROCKCHIP_IOMMU
292 bool "Rockchip IOMMU Support"
293 depends on ARM || ARM64
294 depends on ARCH_ROCKCHIP || COMPILE_TEST
296 select ARM_DMA_USE_IOMMU
298 Support for IOMMUs found on Rockchip rk32xx SOCs.
299 These IOMMUs allow virtualization of the address space used by most
300 cores within the multimedia subsystem.
301 Say Y here if you are using a Rockchip SoC that includes an IOMMU
304 config TEGRA_IOMMU_GART
305 bool "Tegra GART IOMMU Support"
306 depends on ARCH_TEGRA_2x_SOC
310 Enables support for remapping discontiguous physical memory
311 shared with the operating system into contiguous I/O virtual
312 space through the GART (Graphics Address Relocation Table)
313 hardware included on Tegra SoCs.
315 config TEGRA_IOMMU_SMMU
316 bool "NVIDIA Tegra SMMU Support"
317 depends on ARCH_TEGRA
322 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
323 SoCs (Tegra30 up to Tegra210).
326 bool "Exynos IOMMU Support"
327 depends on ARCH_EXYNOS && MMU
328 depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes
330 select ARM_DMA_USE_IOMMU
332 Support for the IOMMU (System MMU) of Samsung Exynos application
333 processor family. This enables H/W multimedia accelerators to see
334 non-linear physical memory chunks as linear memory in their
337 If unsure, say N here.
339 config EXYNOS_IOMMU_DEBUG
340 bool "Debugging log for Exynos IOMMU"
341 depends on EXYNOS_IOMMU
343 Select this to see the detailed log message that shows what
344 happens in the IOMMU driver.
346 Say N unless you need kernel log message for IOMMU debugging.
349 bool "Renesas VMSA-compatible IPMMU"
350 depends on ARM || IOMMU_DMA
351 depends on ARCH_RENESAS || (COMPILE_TEST && !GENERIC_ATOMIC64)
353 select IOMMU_IO_PGTABLE_LPAE
354 select ARM_DMA_USE_IOMMU
356 Support for the Renesas VMSA-compatible IPMMU found in the R-Mobile
357 APE6, R-Car Gen2, and R-Car Gen3 SoCs.
361 config SPAPR_TCE_IOMMU
362 bool "sPAPR TCE IOMMU Support"
363 depends on PPC_POWERNV || PPC_PSERIES
366 Enables bits of IOMMU API required by VFIO. The iommu_ops
367 is not implemented as it is not necessary for VFIO.
371 bool "ARM Ltd. System MMU (SMMU) Support"
372 depends on (ARM64 || ARM) && MMU
374 select IOMMU_IO_PGTABLE_LPAE
375 select ARM_DMA_USE_IOMMU if ARM
377 Support for implementations of the ARM System MMU architecture
380 Say Y here if your SoC includes an IOMMU device implementing
381 the ARM SMMU architecture.
383 config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT
384 bool "Default to disabling bypass on ARM SMMU v1 and v2"
388 Say Y here to (by default) disable bypass streams such that
389 incoming transactions from devices that are not attached to
390 an iommu domain will report an abort back to the device and
391 will not be allowed to pass through the SMMU.
393 Any old kernels that existed before this KConfig was
394 introduced would default to _allowing_ bypass (AKA the
395 equivalent of NO for this config). However the default for
396 this option is YES because the old behavior is insecure.
398 There are few reasons to allow unmatched stream bypass, and
399 even fewer good ones. If saying YES here breaks your board
400 you should work on fixing your board. This KConfig option
401 is expected to be removed in the future and we'll simply
402 hardcode the bypass disable in the code.
404 NOTE: the kernel command line parameter
405 'arm-smmu.disable_bypass' will continue to override this
409 bool "ARM Ltd. System MMU Version 3 (SMMUv3) Support"
412 select IOMMU_IO_PGTABLE_LPAE
413 select GENERIC_MSI_IRQ_DOMAIN
415 Support for implementations of the ARM System MMU architecture
416 version 3 providing translation support to a PCIe root complex.
418 Say Y here if your system includes an IOMMU device implementing
419 the ARM SMMUv3 architecture.
422 def_bool y if S390 && PCI
423 depends on S390 && PCI
426 Support for the IOMMU API for s390 PCI devices.
428 config S390_CCW_IOMMU
429 bool "S390 CCW IOMMU Support"
430 depends on S390 && CCW
433 Enables bits of IOMMU API required by VFIO. The iommu_ops
434 is not implemented as it is not necessary for VFIO.
437 bool "S390 AP IOMMU Support"
438 depends on S390 && ZCRYPT
441 Enables bits of IOMMU API required by VFIO. The iommu_ops
442 is not implemented as it is not necessary for VFIO.
445 bool "MTK IOMMU Support"
446 depends on ARM || ARM64
447 depends on ARCH_MEDIATEK || COMPILE_TEST
448 select ARM_DMA_USE_IOMMU
451 select IOMMU_IO_PGTABLE_ARMV7S
455 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia
456 Memory Management Unit. This option enables remapping of DMA memory
457 accesses for the multimedia subsystem.
459 If unsure, say N here.
462 bool "MTK IOMMU Version 1 (M4U gen1) Support"
464 depends on ARCH_MEDIATEK || COMPILE_TEST
465 select ARM_DMA_USE_IOMMU
470 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is
471 Multimedia Memory Managememt Unit. This option enables remapping of
472 DMA memory accesses for the multimedia subsystem.
474 if unsure, say N here.
477 # Note: iommu drivers cannot (yet?) be built as modules
478 bool "Qualcomm IOMMU Support"
479 depends on ARCH_QCOM || (COMPILE_TEST && !GENERIC_ATOMIC64)
481 select IOMMU_IO_PGTABLE_LPAE
482 select ARM_DMA_USE_IOMMU
484 Support for IOMMU on certain Qualcomm SoCs.
487 bool "Hyper-V x2APIC IRQ Handling"
488 depends on HYPERV && X86
492 Stub IOMMU driver to handle IRQs as to allow Hyper-V Linux
493 guests to run with x2APIC mode enabled.
496 bool "Virtio IOMMU driver"
502 Para-virtualised IOMMU driver with virtio.
504 Say Y here if you intend to run this kernel as a guest.
506 endif # IOMMU_SUPPORT