CONFIG_SPARSE_IRQ: Support sparse irq numbering

General informations

The Linux kernel configuration item CONFIG_SPARSE_IRQ has multiple definitions:

Support sparse irq numbering found in kernel/irq/Kconfig

The configuration item CONFIG_SPARSE_IRQ:

• prompt: Support sparse irq numbering
• type: bool
• depends on: CONFIG_MAY_HAVE_SPARSE_IRQ
• defined in kernel/irq/Kconfig
• found in Linux kernels: 2.6.37–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.12

Help text

Sparse irq numbering is useful for distro kernels that want to define a high NR_CPUS value but still want to have low kernel memory footprint on smaller machines.

( Sparse irqs can also be beneficial on NUMA boxes, as they spread out the interrupt descriptors in a more NUMA-friendly way. )

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

Support sparse irq numbering found in arch/powerpc/Kconfig

The configuration item CONFIG_SPARSE_IRQ:

• prompt: Support sparse irq numbering
• type: bool
• depends on: (none)
• defined in arch/powerpc/Kconfig
• found in Linux kernels: 2.6.33–2.6.37

Help text

This enables support for sparse irqs. This is useful for distro kernels that want to define a high NR_CPUS value but still want to have low kernel memory footprint on smaller machines.

( Sparse IRQs can also be beneficial on NUMA boxes, as they spread out the irq_desc[] array in a more NUMA-friendly way. )

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

found in arch/arm/Kconfig

The configuration item CONFIG_SPARSE_IRQ:

• prompt:
• type: bool
• depends on: (none)
• defined in arch/arm/Kconfig
• found in Linux kernels: 2.6.36–2.6.37

Help text

This enables support for sparse irqs. This is useful in general as most CPUs have a fairly sparse array of IRQ vectors, which the irq_desc then maps directly on to. Systems with a high number of off-chip IRQs will want to treat this as experimental until they have been independently verified.

Support sparse irq numbering found in arch/x86/Kconfig

The configuration item CONFIG_SPARSE_IRQ:

• prompt: Support sparse irq numbering
• type: bool
• depends on: CONFIG_PCI_MSI || CONFIG_HT_IRQ
• defined in arch/x86/Kconfig
• found in Linux kernels: 2.6.29–2.6.36

Help text

This enables support for sparse irqs. This is useful for distro kernels that want to define a high NR_CPUS value but still want to have low kernel memory footprint on smaller machines.

( Sparse IRQs can also be beneficial on NUMA boxes, as they spread out the irq_desc[] array in a more NUMA-friendly way. )

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

found in arch/sh/Kconfig

The configuration item CONFIG_SPARSE_IRQ:

• prompt:
• type: bool
• depends on: CONFIG_SUPERH32
• defined in arch/sh/Kconfig
• found in Linux kernels: 2.6.34–2.6.36

Help text

(none)

Support sparse irq numbering found in arch/sh/Kconfig

The configuration item CONFIG_SPARSE_IRQ:

• prompt: Support sparse irq numbering
• type: bool
• depends on: CONFIG_EXPERIMENTAL
• defined in arch/sh/Kconfig
• found in Linux kernels: 2.6.31–2.6.33

Help text

This enables support for sparse irqs. This is useful in general as most CPUs have a fairly sparse array of IRQ vectors, which the irq_desc then maps directly on to. Systems with a high number of off-chip IRQs will want to treat this as experimental until they have been independently verified.

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

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: