| # |
| # PCI configuration |
| # |
| config ARCH_SUPPORTS_MSI |
| bool |
| default n |
| |
| config PCI_MSI |
| bool "Message Signaled Interrupts (MSI and MSI-X)" |
| depends on PCI |
| depends on ARCH_SUPPORTS_MSI |
| help |
| This allows device drivers to enable MSI (Message Signaled |
| Interrupts). Message Signaled Interrupts enable a device to |
| generate an interrupt using an inbound Memory Write on its |
| PCI bus instead of asserting a device IRQ pin. |
| |
| Use of PCI MSI interrupts can be disabled at kernel boot time |
| by using the 'pci=nomsi' option. This disables MSI for the |
| entire system. |
| |
| If you don't know what to do here, say Y. |
| |
| config PCI_DEBUG |
| bool "PCI Debugging" |
| depends on PCI && DEBUG_KERNEL |
| help |
| Say Y here if you want the PCI core to produce a bunch of debug |
| messages to the system log. Select this if you are having a |
| problem with PCI support and want to see more of what is going on. |
| |
| When in doubt, say N. |
| |
| config PCI_STUB |
| tristate "PCI Stub driver" |
| depends on PCI |
| help |
| Say Y or M here if you want be able to reserve a PCI device |
| when it is going to be assigned to a guest operating system. |
| |
| When in doubt, say N. |
| |
| config XEN_PCIDEV_FRONTEND |
| tristate "Xen PCI Frontend" |
| depends on PCI && X86 && XEN |
| select HOTPLUG |
| select PCI_XEN |
| select XEN_XENBUS_FRONTEND |
| default y |
| help |
| The PCI device frontend driver allows the kernel to import arbitrary |
| PCI devices from a PCI backend to support PCI driver domains. |
| |
| config XEN_PCIDEV_FE_DEBUG |
| bool "Xen PCI Frontend debugging" |
| depends on XEN_PCIDEV_FRONTEND && PCI_DEBUG |
| help |
| Say Y here if you want the Xen PCI frontend to produce a bunch of debug |
| messages to the system log. Select this if you are having a |
| problem with Xen PCI frontend support and want to see more of what is |
| going on. |
| |
| When in doubt, say N. |
| |
| config HT_IRQ |
| bool "Interrupts on hypertransport devices" |
| default y |
| depends on PCI && X86_LOCAL_APIC && X86_IO_APIC |
| help |
| This allows native hypertransport devices to use interrupts. |
| |
| If unsure say Y. |
| |
| config PCI_ATS |
| bool |
| |
| config PCI_IOV |
| bool "PCI IOV support" |
| depends on PCI |
| select PCI_ATS |
| help |
| I/O Virtualization is a PCI feature supported by some devices |
| which allows them to create virtual devices which share their |
| physical resources. |
| |
| If unsure, say N. |
| |
| config PCI_PRI |
| bool "PCI PRI support" |
| select PCI_ATS |
| help |
| PRI is the PCI Page Request Interface. It allows PCI devices that are |
| behind an IOMMU to recover from page faults. |
| |
| If unsure, say N. |
| |
| config PCI_PASID |
| bool "PCI PASID support" |
| depends on PCI |
| select PCI_ATS |
| help |
| Process Address Space Identifiers (PASIDs) can be used by PCI devices |
| to access more than one IO address space at the same time. To make |
| use of this feature an IOMMU is required which also supports PASIDs. |
| Select this option if you have such an IOMMU and want to compile the |
| driver for it into your kernel. |
| |
| If unsure, say N. |
| |
| config PCI_IOAPIC |
| bool |
| depends on PCI |
| depends on ACPI |
| depends on HOTPLUG |
| default y |
| |
| config PCI_LABEL |
| def_bool y if (DMI || ACPI) |
| select NLS |