Kconfig 16.1 KB
Newer Older
1
# SPDX-License-Identifier: GPL-2.0-only
2 3 4 5
# The IOVA library may also be used by non-IOMMU_API users
config IOMMU_IOVA
	tristate

6 7 8 9
# The IOASID library may also be used by non-IOMMU_API users
config IOASID
	tristate

10 11 12
# IOMMU_API always gets selected by whoever wants it.
config IOMMU_API
	bool
13

14 15
menuconfig IOMMU_SUPPORT
	bool "IOMMU Hardware Support"
A
Arnd Bergmann 已提交
16
	depends on MMU
17 18 19 20 21 22 23 24 25
	default y
	---help---
	  Say Y here if you want to compile device drivers for IO Memory
	  Management Units into the kernel. These devices usually allow to
	  remap DMA requests and/or remap interrupts from other devices on the
	  system.

if IOMMU_SUPPORT

26 27 28 29 30 31
menu "Generic IOMMU Pagetable Support"

# Selected by the actual pagetable implementations
config IOMMU_IO_PGTABLE
	bool

32 33 34
config IOMMU_IO_PGTABLE_LPAE
	bool "ARMv7/v8 Long Descriptor Format"
	select IOMMU_IO_PGTABLE
35
	depends on ARM || ARM64 || (COMPILE_TEST && !GENERIC_ATOMIC64)
36 37 38 39 40 41
	help
	  Enable support for the ARM long descriptor pagetable format.
	  This allocator supports 4K/2M/1G, 16K/32M and 64K/512M page
	  sizes at both stage-1 and stage-2, as well as address spaces
	  up to 48-bits in size.

42 43 44 45 46 47 48 49 50
config IOMMU_IO_PGTABLE_LPAE_SELFTEST
	bool "LPAE selftests"
	depends on IOMMU_IO_PGTABLE_LPAE
	help
	  Enable self-tests for LPAE page table allocator. This performs
	  a series of page-table consistency checks during boot.

	  If unsure, say N here.

51 52 53
config IOMMU_IO_PGTABLE_ARMV7S
	bool "ARMv7/v8 Short Descriptor Format"
	select IOMMU_IO_PGTABLE
54
	depends on ARM || ARM64 || COMPILE_TEST
55 56 57 58 59 60 61 62 63 64 65 66 67 68 69
	help
	  Enable support for the ARM Short-descriptor pagetable format.
	  This supports 32-bit virtual and physical addresses mapped using
	  2-level tables with 4KB pages/1MB sections, and contiguous entries
	  for 64KB pages/16MB supersections if indicated by the IOMMU driver.

config IOMMU_IO_PGTABLE_ARMV7S_SELFTEST
	bool "ARMv7s selftests"
	depends on IOMMU_IO_PGTABLE_ARMV7S
	help
	  Enable self-tests for ARMv7s page table allocator. This performs
	  a series of page-table consistency checks during boot.

	  If unsure, say N here.

70 71
endmenu

72 73 74 75 76 77 78 79 80 81
config IOMMU_DEBUGFS
	bool "Export IOMMU internals in DebugFS"
	depends on DEBUG_FS
	help
	  Allows exposure of IOMMU device internals. This option enables
	  the use of debugfs by IOMMU drivers as required. Devices can,
	  at initialization time, cause the IOMMU code to create a top-level
	  debug/iommu directory, and then populate a subdirectory with
	  entries as required.

82 83 84
config IOMMU_DEFAULT_PASSTHROUGH
	bool "IOMMU passthrough by default"
	depends on IOMMU_API
85
	help
86 87 88 89 90 91 92
	  Enable passthrough by default, removing the need to pass in
	  iommu.passthrough=on or iommu=pt through command line. If this
	  is enabled, you can still disable with iommu.passthrough=off
	  or iommu=nopt depending on the architecture.

	  If unsure, say N here.

93
config OF_IOMMU
94 95
	def_bool y
	depends on OF && IOMMU_API
96

97 98 99 100 101
# IOMMU-agnostic DMA-mapping layer
config IOMMU_DMA
	bool
	select IOMMU_API
	select IOMMU_IOVA
102
	select IRQ_MSI_IOMMU
103
	select NEED_SG_DMA_LENGTH
104

105 106
config FSL_PAMU
	bool "Freescale IOMMU support"
107
	depends on PCI
108
	depends on PHYS_64BIT
109
	depends on PPC_E500MC || (COMPILE_TEST && PPC)
110 111 112 113 114 115 116
	select IOMMU_API
	select GENERIC_ALLOCATOR
	help
	  Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
	  PAMU can authorize memory access, remap the memory address, and remap I/O
	  transaction types.

117 118 119
# MSM IOMMU support
config MSM_IOMMU
	bool "MSM IOMMU Support"
120 121
	depends on ARM
	depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST
122
	select IOMMU_API
123
	select IOMMU_IO_PGTABLE_ARMV7S
124 125 126 127 128 129 130 131 132 133
	help
	  Support for the IOMMUs found on certain Qualcomm SOCs.
	  These IOMMUs allow virtualization of the address space used by most
	  cores within the multimedia subsystem.

	  If unsure, say N here.

config IOMMU_PGTABLES_L2
	def_bool y
	depends on MSM_IOMMU && MMU && SMP && CPU_DCACHE_DISABLE=n
134 135 136 137 138 139

# AMD IOMMU support
config AMD_IOMMU
	bool "AMD IOMMU support"
	select SWIOTLB
	select PCI_MSI
140 141 142
	select PCI_ATS
	select PCI_PRI
	select PCI_PASID
143
	select IOMMU_API
144
	select IOMMU_IOVA
145
	select IOMMU_DMA
146
	depends on X86_64 && PCI && ACPI
147 148 149 150
	---help---
	  With this option you can enable support for AMD IOMMU hardware in
	  your system. An IOMMU is a hardware component which provides
	  remapping of DMA memory accesses from devices. With an AMD IOMMU you
M
Masanari Iida 已提交
151
	  can isolate the DMA memory of different devices and protect the
152 153 154 155 156 157
	  system from misbehaving device drivers or hardware.

	  You can find out if your system has an AMD IOMMU if you look into
	  your BIOS for an option to enable it or if you have an IVRS ACPI
	  table.

158
config AMD_IOMMU_V2
159
	tristate "AMD IOMMU Version 2 driver"
160
	depends on AMD_IOMMU
161
	select MMU_NOTIFIER
162 163 164
	---help---
	  This option enables support for the AMD IOMMUv2 features of the IOMMU
	  hardware. Select this option if you want to use devices that support
M
Masanari Iida 已提交
165
	  the PCI PRI and PASID interface.
166

167 168 169 170 171 172 173 174 175 176 177 178
config AMD_IOMMU_DEBUGFS
	bool "Enable AMD IOMMU internals in DebugFS"
	depends on AMD_IOMMU && IOMMU_DEBUGFS
	---help---
	  !!!WARNING!!!  !!!WARNING!!!  !!!WARNING!!!  !!!WARNING!!!

	  DO NOT ENABLE THIS OPTION UNLESS YOU REALLY, -REALLY- KNOW WHAT YOU ARE DOING!!!
	  Exposes AMD IOMMU device internals in DebugFS.

	  This option is -NOT- intended for production environments, and should
	  not generally be enabled.

179
# Intel IOMMU support
180 181 182 183 184
config DMAR_TABLE
	bool

config INTEL_IOMMU
	bool "Support for Intel IOMMU using DMA Remapping Devices"
185
	depends on PCI_MSI && ACPI && (X86 || IA64)
186
	select IOMMU_API
187
	select IOMMU_IOVA
188
	select NEED_DMA_MAP_STATE
189
	select DMAR_TABLE
190
	select SWIOTLB
191
	select IOASID
192 193 194 195 196 197 198
	help
	  DMA remapping (DMAR) devices support enables independent address
	  translations for Direct Memory Access (DMA) from devices.
	  These DMA remapping devices are reported via ACPI tables
	  and include PCI device scope covered by these DMA
	  remapping devices.

199 200 201 202 203 204 205 206 207 208 209 210 211
config INTEL_IOMMU_DEBUGFS
	bool "Export Intel IOMMU internals in Debugfs"
	depends on INTEL_IOMMU && IOMMU_DEBUGFS
	help
	  !!!WARNING!!!

	  DO NOT ENABLE THIS OPTION UNLESS YOU REALLY KNOW WHAT YOU ARE DOING!!!

	  Expose Intel IOMMU internals in Debugfs.

	  This option is -NOT- intended for production environments, and should
	  only be enabled for debugging Intel IOMMU.

212 213 214
config INTEL_IOMMU_SVM
	bool "Support for Shared Virtual Memory with Intel IOMMU"
	depends on INTEL_IOMMU && X86
215
	select PCI_PASID
216
	select PCI_PRI
217
	select MMU_NOTIFIER
218
	select IOASID
219 220 221 222 223
	help
	  Shared Virtual Memory (SVM) provides a facility for devices
	  to access DMA resources through process address space by
	  means of a Process Address Space ID (PASID).

224
config INTEL_IOMMU_DEFAULT_ON
225
	def_bool y
226 227
	prompt "Enable Intel DMA Remapping Devices by default"
	depends on INTEL_IOMMU
228 229 230 231 232
	help
	  Selecting this option will enable a DMAR device at boot time if
	  one is found. If this option is not selected, DMAR support can
	  be enabled by passing intel_iommu=on to the kernel.

233
config INTEL_IOMMU_BROKEN_GFX_WA
234
	bool "Workaround broken graphics drivers (going away soon)"
235
	depends on INTEL_IOMMU && BROKEN && X86
236 237 238 239 240 241 242 243
	---help---
	  Current Graphics drivers tend to use physical address
	  for DMA and avoid using DMA APIs. Setting this config
	  option permits the IOMMU driver to set a unity map for
	  all the OS-visible memory. Hence the driver can continue
	  to use physical addresses for DMA, at least until this
	  option is removed in the 2.6.32 kernel.

244
config INTEL_IOMMU_FLOPPY_WA
245
	def_bool y
246
	depends on INTEL_IOMMU && X86
247 248 249 250 251 252
	---help---
	  Floppy disk drivers are known to bypass DMA API calls
	  thereby failing to work when IOMMU is enabled. This
	  workaround will setup a 1:1 mapping for the first
	  16MiB to make floppy (an ISA device) work.

253 254 255 256 257 258 259 260 261 262 263 264
config INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON
	bool "Enable Intel IOMMU scalable mode by default"
	depends on INTEL_IOMMU
	help
	  Selecting this option will enable by default the scalable mode if
	  hardware presents the capability. The scalable mode is defined in
	  VT-d 3.0. The scalable mode capability could be checked by reading
	  /sys/devices/virtual/iommu/dmar*/intel-iommu/ecap. If this option
	  is not selected, scalable mode support could also be enabled by
	  passing intel_iommu=sm_on to the kernel. If not sure, please use
	  the default value.

265
config IRQ_REMAP
266 267
	bool "Support for Interrupt Remapping"
	depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
268
	select DMAR_TABLE
269 270 271 272
	---help---
	  Supports Interrupt remapping for IO-APIC and MSI devices.
	  To use x2apic mode in the CPU's which support x2APIC enhancements or
	  to support platforms with CPU's having > 8 bit APIC ID, say Y.
273

274 275 276
# OMAP IOMMU support
config OMAP_IOMMU
	bool "OMAP IOMMU Support"
277
	depends on ARM && MMU || (COMPILE_TEST && (ARM || ARM64 || IA64 || SPARC))
278
	depends on ARCH_OMAP2PLUS || COMPILE_TEST
279
	select IOMMU_API
G
Gerd Hoffmann 已提交
280 281 282
	---help---
	  The OMAP3 media platform drivers depend on iommu support,
	  if you need them say Y here.
283 284

config OMAP_IOMMU_DEBUG
285 286 287 288 289
	bool "Export OMAP IOMMU internals in DebugFS"
	depends on OMAP_IOMMU && DEBUG_FS
	---help---
	  Select this to see extensive information about
	  the internal state of OMAP IOMMU in debugfs.
290

291
	  Say N unless you know you need this.
292

D
Daniel Kurtz 已提交
293 294
config ROCKCHIP_IOMMU
	bool "Rockchip IOMMU Support"
295
	depends on ARM || ARM64 || (COMPILE_TEST && (ARM64 || IA64 || SPARC))
296
	depends on ARCH_ROCKCHIP || COMPILE_TEST
D
Daniel Kurtz 已提交
297 298 299 300 301 302 303 304
	select IOMMU_API
	select ARM_DMA_USE_IOMMU
	help
	  Support for IOMMUs found on Rockchip rk32xx SOCs.
	  These IOMMUs allow virtualization of the address space used by most
	  cores within the multimedia subsystem.
	  Say Y here if you are using a Rockchip SoC that includes an IOMMU
	  device.
305

306 307 308 309 310 311 312 313 314
config SUN50I_IOMMU
	bool "Allwinner H6 IOMMU Support"
	depends on ARCH_SUNXI || COMPILE_TEST
	select ARM_DMA_USE_IOMMU
	select IOMMU_API
	select IOMMU_DMA
	help
	  Support for the IOMMU introduced in the Allwinner H6 SoCs.

315 316 317
config TEGRA_IOMMU_GART
	bool "Tegra GART IOMMU Support"
	depends on ARCH_TEGRA_2x_SOC
318
	depends on TEGRA_MC
319 320 321 322 323 324 325
	select IOMMU_API
	help
	  Enables support for remapping discontiguous physical memory
	  shared with the operating system into contiguous I/O virtual
	  space through the GART (Graphics Address Relocation Table)
	  hardware included on Tegra SoCs.

326
config TEGRA_IOMMU_SMMU
327 328 329 330
	bool "NVIDIA Tegra SMMU Support"
	depends on ARCH_TEGRA
	depends on TEGRA_AHB
	depends on TEGRA_MC
331 332
	select IOMMU_API
	help
333
	  This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
334
	  SoCs (Tegra30 up to Tegra210).
335

336 337
config EXYNOS_IOMMU
	bool "Exynos IOMMU Support"
338
	depends on ARCH_EXYNOS && MMU || (COMPILE_TEST && (ARM || ARM64 || IA64 || SPARC))
339
	depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes
340
	select IOMMU_API
341
	select ARM_DMA_USE_IOMMU
342
	help
S
Sachin Kamat 已提交
343 344 345 346
	  Support for the IOMMU (System MMU) of Samsung Exynos application
	  processor family. This enables H/W multimedia accelerators to see
	  non-linear physical memory chunks as linear memory in their
	  address space.
347 348 349 350 351 352 353 354

	  If unsure, say N here.

config EXYNOS_IOMMU_DEBUG
	bool "Debugging log for Exynos IOMMU"
	depends on EXYNOS_IOMMU
	help
	  Select this to see the detailed log message that shows what
S
Sachin Kamat 已提交
355
	  happens in the IOMMU driver.
356

S
Sachin Kamat 已提交
357
	  Say N unless you need kernel log message for IOMMU debugging.
358

359 360
config IPMMU_VMSA
	bool "Renesas VMSA-compatible IPMMU"
361
	depends on ARM || IOMMU_DMA
G
Guenter Roeck 已提交
362
	depends on ARCH_RENESAS || (COMPILE_TEST && !GENERIC_ATOMIC64)
363
	select IOMMU_API
364
	select IOMMU_IO_PGTABLE_LPAE
365 366
	select ARM_DMA_USE_IOMMU
	help
367 368
	  Support for the Renesas VMSA-compatible IPMMU found in the R-Mobile
	  APE6, R-Car Gen2, and R-Car Gen3 SoCs.
369 370 371

	  If unsure, say N.

372 373
config SPAPR_TCE_IOMMU
	bool "sPAPR TCE IOMMU Support"
374
	depends on PPC_POWERNV || PPC_PSERIES
375 376 377 378 379
	select IOMMU_API
	help
	  Enables bits of IOMMU API required by VFIO. The iommu_ops
	  is not implemented as it is not necessary for VFIO.

380
# ARM IOMMU support
381
config ARM_SMMU
382
	tristate "ARM Ltd. System MMU (SMMU) Support"
383
	depends on (ARM64 || ARM || (COMPILE_TEST && !GENERIC_ATOMIC64)) && MMU
384
	select IOMMU_API
385
	select IOMMU_IO_PGTABLE_LPAE
386 387 388
	select ARM_DMA_USE_IOMMU if ARM
	help
	  Support for implementations of the ARM System MMU architecture
389
	  versions 1 and 2.
390 391 392 393

	  Say Y here if your SoC includes an IOMMU device implementing
	  the ARM SMMU architecture.

394 395 396 397 398 399 400 401 402 403 404 405
config ARM_SMMU_LEGACY_DT_BINDINGS
	bool "Support the legacy \"mmu-masters\" devicetree bindings"
	depends on ARM_SMMU=y && OF
	help
	  Support for the badly designed and deprecated "mmu-masters"
	  devicetree bindings. This allows some DMA masters to attach
	  to the SMMU but does not provide any support via the DMA API.
	  If you're lucky, you might be able to get VFIO up and running.

	  If you say Y here then you'll make me very sad. Instead, say N
	  and move your firmware to the utopian future that was 2016.

406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430
config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT
	bool "Default to disabling bypass on ARM SMMU v1 and v2"
	depends on ARM_SMMU
	default y
	help
	  Say Y here to (by default) disable bypass streams such that
	  incoming transactions from devices that are not attached to
	  an iommu domain will report an abort back to the device and
	  will not be allowed to pass through the SMMU.

	  Any old kernels that existed before this KConfig was
	  introduced would default to _allowing_ bypass (AKA the
	  equivalent of NO for this config).  However the default for
	  this option is YES because the old behavior is insecure.

	  There are few reasons to allow unmatched stream bypass, and
	  even fewer good ones.  If saying YES here breaks your board
	  you should work on fixing your board.  This KConfig option
	  is expected to be removed in the future and we'll simply
	  hardcode the bypass disable in the code.

	  NOTE: the kernel command line parameter
	  'arm-smmu.disable_bypass' will continue to override this
	  config.

431
config ARM_SMMU_V3
432
	tristate "ARM Ltd. System MMU Version 3 (SMMUv3) Support"
433
	depends on ARM64
434 435
	select IOMMU_API
	select IOMMU_IO_PGTABLE_LPAE
436
	select GENERIC_MSI_IRQ_DOMAIN
437 438 439 440 441 442 443
	help
	  Support for implementations of the ARM System MMU architecture
	  version 3 providing translation support to a PCIe root complex.

	  Say Y here if your system includes an IOMMU device implementing
	  the ARM SMMUv3 architecture.

444 445 446 447 448 449 450
config S390_IOMMU
	def_bool y if S390 && PCI
	depends on S390 && PCI
	select IOMMU_API
	help
	  Support for the IOMMU API for s390 PCI devices.

451 452
config S390_CCW_IOMMU
	bool "S390 CCW IOMMU Support"
453
	depends on S390 && CCW || COMPILE_TEST
454 455 456 457 458
	select IOMMU_API
	help
	  Enables bits of IOMMU API required by VFIO. The iommu_ops
	  is not implemented as it is not necessary for VFIO.

459 460
config S390_AP_IOMMU
	bool "S390 AP IOMMU Support"
461
	depends on S390 && ZCRYPT || COMPILE_TEST
462 463 464 465 466
	select IOMMU_API
	help
	  Enables bits of IOMMU API required by VFIO. The iommu_ops
	  is not implemented as it is not necessary for VFIO.

467 468
config MTK_IOMMU
	bool "MTK IOMMU Support"
469
	depends on HAS_DMA
470
	depends on ARCH_MEDIATEK || COMPILE_TEST
471
	select ARM_DMA_USE_IOMMU
472 473 474 475 476 477 478 479 480 481 482 483
	select IOMMU_API
	select IOMMU_DMA
	select IOMMU_IO_PGTABLE_ARMV7S
	select MEMORY
	select MTK_SMI
	help
	  Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia
	  Memory Management Unit. This option enables remapping of DMA memory
	  accesses for the multimedia subsystem.

	  If unsure, say N here.

484 485 486 487 488 489 490 491 492 493 494 495 496 497 498
config MTK_IOMMU_V1
	bool "MTK IOMMU Version 1 (M4U gen1) Support"
	depends on ARM
	depends on ARCH_MEDIATEK || COMPILE_TEST
	select ARM_DMA_USE_IOMMU
	select IOMMU_API
	select MEMORY
	select MTK_SMI
	help
	  Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is
	  Multimedia Memory Managememt Unit. This option enables remapping of
	  DMA memory accesses for the multimedia subsystem.

	  if unsure, say N here.

R
Rob Clark 已提交
499 500 501
config QCOM_IOMMU
	# Note: iommu drivers cannot (yet?) be built as modules
	bool "Qualcomm IOMMU Support"
G
Guenter Roeck 已提交
502
	depends on ARCH_QCOM || (COMPILE_TEST && !GENERIC_ATOMIC64)
R
Rob Clark 已提交
503 504 505 506 507 508
	select IOMMU_API
	select IOMMU_IO_PGTABLE_LPAE
	select ARM_DMA_USE_IOMMU
	help
	  Support for IOMMU on certain Qualcomm SoCs.

509 510
config HYPERV_IOMMU
	bool "Hyper-V x2APIC IRQ Handling"
511
	depends on HYPERV && X86
512 513 514 515 516 517
	select IOMMU_API
	default HYPERV
	help
	  Stub IOMMU driver to handle IRQs as to allow Hyper-V Linux
	  guests to run with x2APIC mode enabled.

518
config VIRTIO_IOMMU
519 520
	tristate "Virtio IOMMU driver"
	depends on VIRTIO
521 522 523 524 525 526 527 528
	depends on ARM64
	select IOMMU_API
	select INTERVAL_TREE
	help
	  Para-virtualised IOMMU driver with virtio.

	  Say Y here if you intend to run this kernel as a guest.

529
endif # IOMMU_SUPPORT