CONFIG_PCI_USE_VECTOR: Vector-based interrupt indexing (MSI)

General informations

The Linux kernel configuration item CONFIG_PCI_USE_VECTOR has multiple definitions:

Vector-based interrupt indexing (MSI) found in drivers/pci/Kconfig

The configuration item CONFIG_PCI_USE_VECTOR:

• prompt: Vector-based interrupt indexing (MSI)
• type: bool
• depends on: ( CONFIG_X86_LOCAL_APIC && CONFIG_X86_IO_APIC && ! CONFIG_X86_64 ) || CONFIG_IA64
• defined in drivers/pci/Kconfig
• found in Linux kernels: 2.6.6–2.6.7

Help text

This replaces the current existing IRQ-based index interrupt scheme with the vector-base index scheme. The advantages of vector base over IRQ base are listed below: 1) Support MSI implementation. 2) Support future IOxAPIC hotplug

Note that this allows the device drivers to enable MSI, Message Signaled Interrupt, on all MSI capable device functions detected. Message Signal Interrupt enables an MSI-capable hardware device to send an inbound Memory Write on its PCI bus instead of asserting IRQ signal on device IRQ pin.

If you don't know what to do here, say N.

Vector-based interrupt indexing (MSI) found in arch/i386/Kconfig

The configuration item CONFIG_PCI_USE_VECTOR:

• prompt: Vector-based interrupt indexing (MSI)
• type: bool
• depends on: CONFIG_X86_LOCAL_APIC && CONFIG_X86_IO_APIC
• defined in arch/i386/Kconfig
• found in Linux kernels: 2.6.4–2.6.5

Help text

This replaces the current existing IRQ-based index interrupt scheme with the vector-base index scheme. The advantages of vector base over IRQ base are listed below: 1) Support MSI implementation. 2) Support future IOxAPIC hotplug

Note that this allows the device drivers to enable MSI, Message Signaled Interrupt, on all MSI capable device functions detected. Message Signal Interrupt enables an MSI-capable hardware device to send an inbound Memory Write on its PCI bus instead of asserting IRQ signal on device IRQ pin.

If you don't know what to do here, say N.

Vector-based interrupt indexing found in arch/x86_64/Kconfig

The configuration item CONFIG_PCI_USE_VECTOR:

• prompt: Vector-based interrupt indexing
• type: bool
• depends on: CONFIG_X86_LOCAL_APIC && CONFIG_NOTWORKING
• defined in arch/x86_64/Kconfig
• found in Linux kernels: 2.6.2–2.6.5

Help text

This replaces the current existing IRQ-based index interrupt scheme with the vector-base index scheme. The advantages of vector base over IRQ base are listed below: 1) Support MSI implementation. 2) Support future IOxAPIC hotplug

Note that this enables MSI, Message Signaled Interrupt, on all MSI capable device functions detected if users also install the MSI patch. Message Signal Interrupt enables an MSI-capable hardware device to send an inbound Memory Write on its PCI bus instead of asserting IRQ signal on device IRQ pin.

If you don't know what to do here, say N.

Vector-based interrupt indexing found in arch/i386/Kconfig

The configuration item CONFIG_PCI_USE_VECTOR:

• prompt: Vector-based interrupt indexing
• type: bool
• depends on: CONFIG_X86_LOCAL_APIC && CONFIG_X86_IO_APIC
• defined in arch/i386/Kconfig
• found in Linux kernels: 2.6.1–2.6.3

Help text

This replaces the current existing IRQ-based index interrupt scheme with the vector-base index scheme. The advantages of vector base over IRQ base are listed below: 1) Support MSI implementation. 2) Support future IOxAPIC hotplug

Note that this enables MSI, Message Signaled Interrupt, on all MSI capable device functions detected if users also install the MSI patch. Message Signal Interrupt enables an MSI-capable hardware device to send an inbound Memory Write on its PCI bus instead of asserting IRQ signal on device IRQ pin.

If you don't know what to do here, say N.

found in arch/x86_64/Kconfig

The configuration item CONFIG_PCI_USE_VECTOR:

• prompt:
• type: bool
• depends on: (none)
• defined in arch/x86_64/Kconfig
• found in Linux kernels: 2.6.1

Help text

(none)

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: