Kconfig 3.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121
  1. #
  2. # PCI configuration
  3. #
  4. config ARCH_SUPPORTS_MSI
  5. bool
  6. config PCI_MSI
  7. bool "Message Signaled Interrupts (MSI and MSI-X)"
  8. depends on PCI
  9. depends on ARCH_SUPPORTS_MSI
  10. help
  11. This allows device drivers to enable MSI (Message Signaled
  12. Interrupts). Message Signaled Interrupts enable a device to
  13. generate an interrupt using an inbound Memory Write on its
  14. PCI bus instead of asserting a device IRQ pin.
  15. Use of PCI MSI interrupts can be disabled at kernel boot time
  16. by using the 'pci=nomsi' option. This disables MSI for the
  17. entire system.
  18. If you don't know what to do here, say Y.
  19. config PCI_DEBUG
  20. bool "PCI Debugging"
  21. depends on PCI && DEBUG_KERNEL
  22. help
  23. Say Y here if you want the PCI core to produce a bunch of debug
  24. messages to the system log. Select this if you are having a
  25. problem with PCI support and want to see more of what is going on.
  26. When in doubt, say N.
  27. config PCI_REALLOC_ENABLE_AUTO
  28. bool "Enable PCI resource re-allocation detection"
  29. depends on PCI
  30. help
  31. Say Y here if you want the PCI core to detect if PCI resource
  32. re-allocation needs to be enabled. You can always use pci=realloc=on
  33. or pci=realloc=off to override it. Note this feature is a no-op
  34. unless PCI_IOV support is also enabled; in that case it will
  35. automatically re-allocate PCI resources if SR-IOV BARs have not
  36. been allocated by the BIOS.
  37. When in doubt, say N.
  38. config PCI_STUB
  39. tristate "PCI Stub driver"
  40. depends on PCI
  41. help
  42. Say Y or M here if you want be able to reserve a PCI device
  43. when it is going to be assigned to a guest operating system.
  44. When in doubt, say N.
  45. config XEN_PCIDEV_FRONTEND
  46. tristate "Xen PCI Frontend"
  47. depends on PCI && X86 && XEN
  48. select PCI_XEN
  49. select XEN_XENBUS_FRONTEND
  50. default y
  51. help
  52. The PCI device frontend driver allows the kernel to import arbitrary
  53. PCI devices from a PCI backend to support PCI driver domains.
  54. config HT_IRQ
  55. bool "Interrupts on hypertransport devices"
  56. default y
  57. depends on PCI && X86_LOCAL_APIC && X86_IO_APIC
  58. help
  59. This allows native hypertransport devices to use interrupts.
  60. If unsure say Y.
  61. config PCI_ATS
  62. bool
  63. config PCI_IOV
  64. bool "PCI IOV support"
  65. depends on PCI
  66. select PCI_ATS
  67. help
  68. I/O Virtualization is a PCI feature supported by some devices
  69. which allows them to create virtual devices which share their
  70. physical resources.
  71. If unsure, say N.
  72. config PCI_PRI
  73. bool "PCI PRI support"
  74. depends on PCI
  75. select PCI_ATS
  76. help
  77. PRI is the PCI Page Request Interface. It allows PCI devices that are
  78. behind an IOMMU to recover from page faults.
  79. If unsure, say N.
  80. config PCI_PASID
  81. bool "PCI PASID support"
  82. depends on PCI
  83. select PCI_ATS
  84. help
  85. Process Address Space Identifiers (PASIDs) can be used by PCI devices
  86. to access more than one IO address space at the same time. To make
  87. use of this feature an IOMMU is required which also supports PASIDs.
  88. Select this option if you have such an IOMMU and want to compile the
  89. driver for it into your kernel.
  90. If unsure, say N.
  91. config PCI_IOAPIC
  92. tristate "PCI IO-APIC hotplug support" if X86
  93. depends on PCI
  94. depends on ACPI
  95. default !X86
  96. config PCI_LABEL
  97. def_bool y if (DMI || ACPI)
  98. select NLS
  99. source "drivers/pci/host/Kconfig"