11da177e4SLinus Torvalds# 21da177e4SLinus Torvalds# PCI configuration 31da177e4SLinus Torvalds# 4f282b970SDan Williamsconfig ARCH_SUPPORTS_MSI 5f282b970SDan Williams bool 6f282b970SDan Williams default n 7f282b970SDan Williams 81da177e4SLinus Torvaldsconfig PCI_MSI 91da177e4SLinus Torvalds bool "Message Signaled Interrupts (MSI and MSI-X)" 101da177e4SLinus Torvalds depends on PCI 11f282b970SDan Williams depends on ARCH_SUPPORTS_MSI 121da177e4SLinus Torvalds help 131da177e4SLinus Torvalds This allows device drivers to enable MSI (Message Signaled 141da177e4SLinus Torvalds Interrupts). Message Signaled Interrupts enable a device to 151da177e4SLinus Torvalds generate an interrupt using an inbound Memory Write on its 161da177e4SLinus Torvalds PCI bus instead of asserting a device IRQ pin. 171da177e4SLinus Torvalds 18309e57dfSMatthew Wilcox Use of PCI MSI interrupts can be disabled at kernel boot time 19309e57dfSMatthew Wilcox by using the 'pci=nomsi' option. This disables MSI for the 20309e57dfSMatthew Wilcox entire system. 21309e57dfSMatthew Wilcox 221da177e4SLinus Torvalds If you don't know what to do here, say N. 231da177e4SLinus Torvalds 240f397f86SGreg Kroah-Hartmanconfig PCI_MULTITHREAD_PROBE 250f397f86SGreg Kroah-Hartman bool "PCI Multi-threaded probe (EXPERIMENTAL)" 26fd8d4b11SAndrew Morton depends on PCI && EXPERIMENTAL && BROKEN 270f397f86SGreg Kroah-Hartman help 280f397f86SGreg Kroah-Hartman Say Y here if you want the PCI core to spawn a new thread for 290f397f86SGreg Kroah-Hartman every PCI device that is probed. This can cause a huge 300f397f86SGreg Kroah-Hartman speedup in boot times on multiprocessor machines, and even a 310f397f86SGreg Kroah-Hartman smaller speedup on single processor machines. 320f397f86SGreg Kroah-Hartman 330f397f86SGreg Kroah-Hartman But it can also cause lots of bad things to happen. A number 340f397f86SGreg Kroah-Hartman of PCI drivers cannot properly handle running in this way, 350f397f86SGreg Kroah-Hartman some will just not work properly at all, while others might 360f397f86SGreg Kroah-Hartman decide to blow up power supplies with a huge load all at once, 370f397f86SGreg Kroah-Hartman so use this option at your own risk. 380f397f86SGreg Kroah-Hartman 390f397f86SGreg Kroah-Hartman It is very unwise to use this option if you are not using a 400f397f86SGreg Kroah-Hartman boot process that can handle devices being created in any 4103a67a46SJan Engelhardt order. A program that can create persistent block and network 420f397f86SGreg Kroah-Hartman device names (like udev) is a good idea if you wish to use 430f397f86SGreg Kroah-Hartman this option. 440f397f86SGreg Kroah-Hartman 450f397f86SGreg Kroah-Hartman Again, use this option at your own risk, you have been warned! 460f397f86SGreg Kroah-Hartman 470f397f86SGreg Kroah-Hartman When in doubt, say N. 480f397f86SGreg Kroah-Hartman 491da177e4SLinus Torvaldsconfig PCI_DEBUG 501da177e4SLinus Torvalds bool "PCI Debugging" 511da177e4SLinus Torvalds depends on PCI && DEBUG_KERNEL 521da177e4SLinus Torvalds help 531da177e4SLinus Torvalds Say Y here if you want the PCI core to produce a bunch of debug 541da177e4SLinus Torvalds messages to the system log. Select this if you are having a 551da177e4SLinus Torvalds problem with PCI support and want to see more of what is going on. 561da177e4SLinus Torvalds 571da177e4SLinus Torvalds When in doubt, say N. 581da177e4SLinus Torvalds 598b955b0dSEric W. Biedermanconfig HT_IRQ 608b955b0dSEric W. Biederman bool "Interrupts on hypertransport devices" 618b955b0dSEric W. Biederman default y 62fbab41ccSAdrian Bunk depends on PCI && X86_LOCAL_APIC && X86_IO_APIC 638b955b0dSEric W. Biederman help 648b955b0dSEric W. Biederman This allows native hypertransport devices to use interrupts. 658b955b0dSEric W. Biederman 668b955b0dSEric W. Biederman If unsure say Y. 67