| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # |
| 2 | # PCI configuration |
| 3 | # |
| Dan Williams | f282b97 | 2007-04-18 18:46:20 +1000 | [diff] [blame] | 4 | config ARCH_SUPPORTS_MSI |
| 5 | bool |
| 6 | default n |
| 7 | |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 8 | config PCI_MSI |
| 9 | bool "Message Signaled Interrupts (MSI and MSI-X)" |
| 10 | depends on PCI |
| Dan Williams | f282b97 | 2007-04-18 18:46:20 +1000 | [diff] [blame] | 11 | depends on ARCH_SUPPORTS_MSI |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 12 | help |
| 13 | This allows device drivers to enable MSI (Message Signaled |
| 14 | Interrupts). Message Signaled Interrupts enable a device to |
| 15 | generate an interrupt using an inbound Memory Write on its |
| 16 | PCI bus instead of asserting a device IRQ pin. |
| 17 | |
| Matthew Wilcox | 309e57d | 2006-03-05 22:33:34 -0700 | [diff] [blame] | 18 | Use of PCI MSI interrupts can be disabled at kernel boot time |
| 19 | by using the 'pci=nomsi' option. This disables MSI for the |
| 20 | entire system. |
| 21 | |
| Jesse Barnes | 3196180 | 2010-04-08 09:38:47 -0700 | [diff] [blame] | 22 | If you don't know what to do here, say Y. |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 23 | |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 24 | config PCI_DEBUG |
| 25 | bool "PCI Debugging" |
| 26 | depends on PCI && DEBUG_KERNEL |
| 27 | help |
| 28 | Say Y here if you want the PCI core to produce a bunch of debug |
| 29 | messages to the system log. Select this if you are having a |
| 30 | problem with PCI support and want to see more of what is going on. |
| 31 | |
| 32 | When in doubt, say N. |
| 33 | |
| Chris Wright | c70e0d9 | 2008-11-25 21:17:13 -0800 | [diff] [blame] | 34 | config PCI_STUB |
| 35 | tristate "PCI Stub driver" |
| 36 | depends on PCI |
| 37 | help |
| 38 | Say Y or M here if you want be able to reserve a PCI device |
| 39 | when it is going to be assigned to a guest operating system. |
| 40 | |
| 41 | When in doubt, say N. |
| 42 | |
| Eric W. Biederman | 8b955b0 | 2006-10-04 02:16:55 -0700 | [diff] [blame] | 43 | config HT_IRQ |
| 44 | bool "Interrupts on hypertransport devices" |
| 45 | default y |
| Adrian Bunk | fbab41c | 2006-10-11 01:22:04 -0700 | [diff] [blame] | 46 | depends on PCI && X86_LOCAL_APIC && X86_IO_APIC |
| Eric W. Biederman | 8b955b0 | 2006-10-04 02:16:55 -0700 | [diff] [blame] | 47 | help |
| 48 | This allows native hypertransport devices to use interrupts. |
| 49 | |
| 50 | If unsure say Y. |
| Yu Zhao | d1b054d | 2009-03-20 11:25:11 +0800 | [diff] [blame] | 51 | |
| 52 | config PCI_IOV |
| 53 | bool "PCI IOV support" |
| 54 | depends on PCI |
| 55 | help |
| 56 | I/O Virtualization is a PCI feature supported by some devices |
| 57 | which allows them to create virtual devices which share their |
| 58 | physical resources. |
| 59 | |
| 60 | If unsure, say N. |
| Bjorn Helgaas | 204d49a | 2009-10-26 11:20:47 -0600 | [diff] [blame] | 61 | |
| 62 | config PCI_IOAPIC |
| 63 | bool |
| 64 | depends on PCI |
| 65 | depends on ACPI |
| 66 | depends on HOTPLUG |
| 67 | default y |