Kconfig 3.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697
  1. # IOMMU_API always gets selected by whoever wants it.
  2. config IOMMU_API
  3. bool
  4. # MSM IOMMU support
  5. config MSM_IOMMU
  6. bool "MSM IOMMU Support"
  7. depends on ARCH_MSM8X60 || ARCH_MSM8960
  8. select IOMMU_API
  9. help
  10. Support for the IOMMUs found on certain Qualcomm SOCs.
  11. These IOMMUs allow virtualization of the address space used by most
  12. cores within the multimedia subsystem.
  13. If unsure, say N here.
  14. config IOMMU_PGTABLES_L2
  15. def_bool y
  16. depends on MSM_IOMMU && MMU && SMP && CPU_DCACHE_DISABLE=n
  17. # AMD IOMMU support
  18. config AMD_IOMMU
  19. bool "AMD IOMMU support"
  20. select SWIOTLB
  21. select PCI_MSI
  22. select PCI_IOV
  23. select IOMMU_API
  24. depends on X86_64 && PCI && ACPI
  25. ---help---
  26. With this option you can enable support for AMD IOMMU hardware in
  27. your system. An IOMMU is a hardware component which provides
  28. remapping of DMA memory accesses from devices. With an AMD IOMMU you
  29. can isolate the the DMA memory of different devices and protect the
  30. system from misbehaving device drivers or hardware.
  31. You can find out if your system has an AMD IOMMU if you look into
  32. your BIOS for an option to enable it or if you have an IVRS ACPI
  33. table.
  34. config AMD_IOMMU_STATS
  35. bool "Export AMD IOMMU statistics to debugfs"
  36. depends on AMD_IOMMU
  37. select DEBUG_FS
  38. ---help---
  39. This option enables code in the AMD IOMMU driver to collect various
  40. statistics about whats happening in the driver and exports that
  41. information to userspace via debugfs.
  42. If unsure, say N.
  43. # Intel IOMMU support
  44. config DMAR
  45. bool "Support for DMA Remapping Devices"
  46. depends on PCI_MSI && ACPI && (X86 || IA64_GENERIC)
  47. select IOMMU_API
  48. help
  49. DMA remapping (DMAR) devices support enables independent address
  50. translations for Direct Memory Access (DMA) from devices.
  51. These DMA remapping devices are reported via ACPI tables
  52. and include PCI device scope covered by these DMA
  53. remapping devices.
  54. config DMAR_DEFAULT_ON
  55. def_bool y
  56. prompt "Enable DMA Remapping Devices by default"
  57. depends on DMAR
  58. help
  59. Selecting this option will enable a DMAR device at boot time if
  60. one is found. If this option is not selected, DMAR support can
  61. be enabled by passing intel_iommu=on to the kernel.
  62. config DMAR_BROKEN_GFX_WA
  63. bool "Workaround broken graphics drivers (going away soon)"
  64. depends on DMAR && BROKEN && X86
  65. ---help---
  66. Current Graphics drivers tend to use physical address
  67. for DMA and avoid using DMA APIs. Setting this config
  68. option permits the IOMMU driver to set a unity map for
  69. all the OS-visible memory. Hence the driver can continue
  70. to use physical addresses for DMA, at least until this
  71. option is removed in the 2.6.32 kernel.
  72. config DMAR_FLOPPY_WA
  73. def_bool y
  74. depends on DMAR && X86
  75. ---help---
  76. Floppy disk drivers are known to bypass DMA API calls
  77. thereby failing to work when IOMMU is enabled. This
  78. workaround will setup a 1:1 mapping for the first
  79. 16MiB to make floppy (an ISA device) work.
  80. config INTR_REMAP
  81. bool "Support for Interrupt Remapping (EXPERIMENTAL)"
  82. depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI && EXPERIMENTAL
  83. ---help---
  84. Supports Interrupt remapping for IO-APIC and MSI devices.
  85. To use x2apic mode in the CPU's which support x2APIC enhancements or
  86. to support platforms with CPU's having > 8 bit APIC ID, say Y.