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