| .. | .. |
|---|
| 3 | 3 | # PCI configuration |
|---|
| 4 | 4 | # |
|---|
| 5 | 5 | |
|---|
| 6 | +# select this to offer the PCI prompt |
|---|
| 7 | +config HAVE_PCI |
|---|
| 8 | + bool |
|---|
| 9 | + |
|---|
| 10 | +# select this to unconditionally force on PCI support |
|---|
| 11 | +config FORCE_PCI |
|---|
| 12 | + bool |
|---|
| 13 | + select HAVE_PCI |
|---|
| 14 | + select PCI |
|---|
| 15 | + |
|---|
| 16 | +menuconfig PCI |
|---|
| 17 | + bool "PCI support" |
|---|
| 18 | + depends on HAVE_PCI |
|---|
| 19 | + help |
|---|
| 20 | + This option enables support for the PCI local bus, including |
|---|
| 21 | + support for PCI-X and the foundations for PCI Express support. |
|---|
| 22 | + Say 'Y' here unless you know what you are doing. |
|---|
| 23 | + |
|---|
| 24 | +if PCI |
|---|
| 25 | + |
|---|
| 26 | +config PCI_DOMAINS |
|---|
| 27 | + bool |
|---|
| 28 | + depends on PCI |
|---|
| 29 | + |
|---|
| 30 | +config PCI_DOMAINS_GENERIC |
|---|
| 31 | + bool |
|---|
| 32 | + select PCI_DOMAINS |
|---|
| 33 | + |
|---|
| 34 | +config PCI_SYSCALL |
|---|
| 35 | + bool |
|---|
| 36 | + |
|---|
| 6 | 37 | source "drivers/pci/pcie/Kconfig" |
|---|
| 7 | 38 | |
|---|
| 8 | 39 | config PCI_MSI |
|---|
| 9 | 40 | bool "Message Signaled Interrupts (MSI and MSI-X)" |
|---|
| 10 | | - depends on PCI |
|---|
| 11 | 41 | select GENERIC_MSI_IRQ |
|---|
| 12 | 42 | help |
|---|
| 13 | 43 | This allows device drivers to enable MSI (Message Signaled |
|---|
| .. | .. |
|---|
| 22 | 52 | If you don't know what to do here, say Y. |
|---|
| 23 | 53 | |
|---|
| 24 | 54 | config PCI_MSI_IRQ_DOMAIN |
|---|
| 25 | | - def_bool ARC || ARM || ARM64 || X86 |
|---|
| 55 | + def_bool y |
|---|
| 26 | 56 | depends on PCI_MSI |
|---|
| 27 | 57 | select GENERIC_MSI_IRQ_DOMAIN |
|---|
| 58 | + |
|---|
| 59 | +config PCI_MSI_ARCH_FALLBACKS |
|---|
| 60 | + bool |
|---|
| 28 | 61 | |
|---|
| 29 | 62 | config PCI_QUIRKS |
|---|
| 30 | 63 | default y |
|---|
| 31 | 64 | bool "Enable PCI quirk workarounds" if EXPERT |
|---|
| 32 | | - depends on PCI |
|---|
| 33 | 65 | help |
|---|
| 34 | 66 | This enables workarounds for various PCI chipset bugs/quirks. |
|---|
| 35 | 67 | Disable this only if your target machine is unaffected by PCI |
|---|
| .. | .. |
|---|
| 37 | 69 | |
|---|
| 38 | 70 | config PCI_DEBUG |
|---|
| 39 | 71 | bool "PCI Debugging" |
|---|
| 40 | | - depends on PCI && DEBUG_KERNEL |
|---|
| 72 | + depends on DEBUG_KERNEL |
|---|
| 41 | 73 | help |
|---|
| 42 | 74 | Say Y here if you want the PCI core to produce a bunch of debug |
|---|
| 43 | 75 | messages to the system log. Select this if you are having a |
|---|
| .. | .. |
|---|
| 47 | 79 | |
|---|
| 48 | 80 | config PCI_REALLOC_ENABLE_AUTO |
|---|
| 49 | 81 | bool "Enable PCI resource re-allocation detection" |
|---|
| 50 | | - depends on PCI |
|---|
| 51 | 82 | depends on PCI_IOV |
|---|
| 52 | 83 | help |
|---|
| 53 | 84 | Say Y here if you want the PCI core to detect if PCI resource |
|---|
| .. | .. |
|---|
| 60 | 91 | |
|---|
| 61 | 92 | config PCI_STUB |
|---|
| 62 | 93 | tristate "PCI Stub driver" |
|---|
| 63 | | - depends on PCI |
|---|
| 64 | 94 | help |
|---|
| 65 | 95 | Say Y or M here if you want be able to reserve a PCI device |
|---|
| 66 | 96 | when it is going to be assigned to a guest operating system. |
|---|
| .. | .. |
|---|
| 69 | 99 | |
|---|
| 70 | 100 | config PCI_PF_STUB |
|---|
| 71 | 101 | tristate "PCI PF Stub driver" |
|---|
| 72 | | - depends on PCI |
|---|
| 73 | 102 | depends on PCI_IOV |
|---|
| 74 | 103 | help |
|---|
| 75 | 104 | Say Y or M here if you want to enable support for devices that |
|---|
| 76 | | - require SR-IOV support, while at the same time the PF itself is |
|---|
| 77 | | - not providing any actual services on the host itself such as |
|---|
| 78 | | - storage or networking. |
|---|
| 105 | + require SR-IOV support, while at the same time the PF (Physical |
|---|
| 106 | + Function) itself is not providing any actual services on the |
|---|
| 107 | + host itself such as storage or networking. |
|---|
| 79 | 108 | |
|---|
| 80 | 109 | When in doubt, say N. |
|---|
| 81 | 110 | |
|---|
| 82 | 111 | config XEN_PCIDEV_FRONTEND |
|---|
| 83 | | - tristate "Xen PCI Frontend" |
|---|
| 84 | | - depends on PCI && X86 && XEN |
|---|
| 85 | | - select PCI_XEN |
|---|
| 112 | + tristate "Xen PCI Frontend" |
|---|
| 113 | + depends on X86 && XEN |
|---|
| 114 | + select PCI_XEN |
|---|
| 86 | 115 | select XEN_XENBUS_FRONTEND |
|---|
| 87 | | - default y |
|---|
| 88 | | - help |
|---|
| 89 | | - The PCI device frontend driver allows the kernel to import arbitrary |
|---|
| 90 | | - PCI devices from a PCI backend to support PCI driver domains. |
|---|
| 116 | + default y |
|---|
| 117 | + help |
|---|
| 118 | + The PCI device frontend driver allows the kernel to import arbitrary |
|---|
| 119 | + PCI devices from a PCI backend to support PCI driver domains. |
|---|
| 91 | 120 | |
|---|
| 92 | 121 | config PCI_ATS |
|---|
| 93 | 122 | bool |
|---|
| .. | .. |
|---|
| 98 | 127 | config PCI_LOCKLESS_CONFIG |
|---|
| 99 | 128 | bool |
|---|
| 100 | 129 | |
|---|
| 130 | +config PCI_BRIDGE_EMUL |
|---|
| 131 | + bool |
|---|
| 132 | + |
|---|
| 101 | 133 | config PCI_IOV |
|---|
| 102 | 134 | bool "PCI IOV support" |
|---|
| 103 | | - depends on PCI |
|---|
| 104 | 135 | select PCI_ATS |
|---|
| 105 | 136 | help |
|---|
| 106 | 137 | I/O Virtualization is a PCI feature supported by some devices |
|---|
| .. | .. |
|---|
| 111 | 142 | |
|---|
| 112 | 143 | config PCI_PRI |
|---|
| 113 | 144 | bool "PCI PRI support" |
|---|
| 114 | | - depends on PCI |
|---|
| 115 | 145 | select PCI_ATS |
|---|
| 116 | 146 | help |
|---|
| 117 | 147 | PRI is the PCI Page Request Interface. It allows PCI devices that are |
|---|
| .. | .. |
|---|
| 121 | 151 | |
|---|
| 122 | 152 | config PCI_PASID |
|---|
| 123 | 153 | bool "PCI PASID support" |
|---|
| 124 | | - depends on PCI |
|---|
| 125 | 154 | select PCI_ATS |
|---|
| 126 | 155 | help |
|---|
| 127 | 156 | Process Address Space Identifiers (PASIDs) can be used by PCI devices |
|---|
| .. | .. |
|---|
| 132 | 161 | |
|---|
| 133 | 162 | If unsure, say N. |
|---|
| 134 | 163 | |
|---|
| 164 | +config PCI_P2PDMA |
|---|
| 165 | + bool "PCI peer-to-peer transfer support" |
|---|
| 166 | + depends on ZONE_DEVICE |
|---|
| 167 | + select GENERIC_ALLOCATOR |
|---|
| 168 | + help |
|---|
| 169 | + Enableѕ drivers to do PCI peer-to-peer transactions to and from |
|---|
| 170 | + BARs that are exposed in other devices that are the part of |
|---|
| 171 | + the hierarchy where peer-to-peer DMA is guaranteed by the PCI |
|---|
| 172 | + specification to work (ie. anything below a single PCI bridge). |
|---|
| 173 | + |
|---|
| 174 | + Many PCIe root complexes do not support P2P transactions and |
|---|
| 175 | + it's hard to tell which support it at all, so at this time, |
|---|
| 176 | + P2P DMA transactions must be between devices behind the same root |
|---|
| 177 | + port. |
|---|
| 178 | + |
|---|
| 179 | + If unsure, say N. |
|---|
| 180 | + |
|---|
| 135 | 181 | config PCI_LABEL |
|---|
| 136 | 182 | def_bool y if (DMI || ACPI) |
|---|
| 137 | | - depends on PCI |
|---|
| 138 | 183 | select NLS |
|---|
| 139 | 184 | |
|---|
| 140 | 185 | config PCI_HYPERV |
|---|
| 141 | | - tristate "Hyper-V PCI Frontend" |
|---|
| 142 | | - depends on PCI && X86 && HYPERV && PCI_MSI && PCI_MSI_IRQ_DOMAIN && X86_64 |
|---|
| 143 | | - help |
|---|
| 144 | | - The PCI device frontend driver allows the kernel to import arbitrary |
|---|
| 145 | | - PCI devices from a PCI backend to support PCI driver domains. |
|---|
| 186 | + tristate "Hyper-V PCI Frontend" |
|---|
| 187 | + depends on X86_64 && HYPERV && PCI_MSI && PCI_MSI_IRQ_DOMAIN && SYSFS |
|---|
| 188 | + select PCI_HYPERV_INTERFACE |
|---|
| 189 | + help |
|---|
| 190 | + The PCI device frontend driver allows the kernel to import arbitrary |
|---|
| 191 | + PCI devices from a PCI backend to support PCI driver domains. |
|---|
| 192 | + |
|---|
| 193 | +choice |
|---|
| 194 | + prompt "PCI Express hierarchy optimization setting" |
|---|
| 195 | + default PCIE_BUS_DEFAULT |
|---|
| 196 | + depends on PCI && EXPERT |
|---|
| 197 | + help |
|---|
| 198 | + MPS (Max Payload Size) and MRRS (Max Read Request Size) are PCIe |
|---|
| 199 | + device parameters that affect performance and the ability to |
|---|
| 200 | + support hotplug and peer-to-peer DMA. |
|---|
| 201 | + |
|---|
| 202 | + The following choices set the MPS and MRRS optimization strategy |
|---|
| 203 | + at compile-time. The choices are the same as those offered for |
|---|
| 204 | + the kernel command-line parameter 'pci', i.e., |
|---|
| 205 | + 'pci=pcie_bus_tune_off', 'pci=pcie_bus_safe', |
|---|
| 206 | + 'pci=pcie_bus_perf', and 'pci=pcie_bus_peer2peer'. |
|---|
| 207 | + |
|---|
| 208 | + This is a compile-time setting and can be overridden by the above |
|---|
| 209 | + command-line parameters. If unsure, choose PCIE_BUS_DEFAULT. |
|---|
| 210 | + |
|---|
| 211 | +config PCIE_BUS_TUNE_OFF |
|---|
| 212 | + bool "Tune Off" |
|---|
| 213 | + depends on PCI |
|---|
| 214 | + help |
|---|
| 215 | + Use the BIOS defaults; don't touch MPS at all. This is the same |
|---|
| 216 | + as booting with 'pci=pcie_bus_tune_off'. |
|---|
| 217 | + |
|---|
| 218 | +config PCIE_BUS_DEFAULT |
|---|
| 219 | + bool "Default" |
|---|
| 220 | + depends on PCI |
|---|
| 221 | + help |
|---|
| 222 | + Default choice; ensure that the MPS matches upstream bridge. |
|---|
| 223 | + |
|---|
| 224 | +config PCIE_BUS_SAFE |
|---|
| 225 | + bool "Safe" |
|---|
| 226 | + depends on PCI |
|---|
| 227 | + help |
|---|
| 228 | + Use largest MPS that boot-time devices support. If you have a |
|---|
| 229 | + closed system with no possibility of adding new devices, this |
|---|
| 230 | + will use the largest MPS that's supported by all devices. This |
|---|
| 231 | + is the same as booting with 'pci=pcie_bus_safe'. |
|---|
| 232 | + |
|---|
| 233 | +config PCIE_BUS_PERFORMANCE |
|---|
| 234 | + bool "Performance" |
|---|
| 235 | + depends on PCI |
|---|
| 236 | + help |
|---|
| 237 | + Use MPS and MRRS for best performance. Ensure that a given |
|---|
| 238 | + device's MPS is no larger than its parent MPS, which allows us to |
|---|
| 239 | + keep all switches/bridges to the max MPS supported by their |
|---|
| 240 | + parent. This is the same as booting with 'pci=pcie_bus_perf'. |
|---|
| 241 | + |
|---|
| 242 | +config PCIE_BUS_PEER2PEER |
|---|
| 243 | + bool "Peer2peer" |
|---|
| 244 | + depends on PCI |
|---|
| 245 | + help |
|---|
| 246 | + Set MPS = 128 for all devices. MPS configuration effected by the |
|---|
| 247 | + other options could cause the MPS on one root port to be |
|---|
| 248 | + different than that of the MPS on another, which may cause |
|---|
| 249 | + hot-added devices or peer-to-peer DMA to fail. Set MPS to the |
|---|
| 250 | + smallest possible value (128B) system-wide to avoid these issues. |
|---|
| 251 | + This is the same as booting with 'pci=pcie_bus_peer2peer'. |
|---|
| 252 | + |
|---|
| 253 | +endchoice |
|---|
| 146 | 254 | |
|---|
| 147 | 255 | source "drivers/pci/hotplug/Kconfig" |
|---|
| 148 | 256 | source "drivers/pci/controller/Kconfig" |
|---|
| 149 | 257 | source "drivers/pci/endpoint/Kconfig" |
|---|
| 150 | 258 | source "drivers/pci/switch/Kconfig" |
|---|
| 259 | + |
|---|
| 260 | +endif |
|---|