Re: [patch 18/19] genirq: Provide Kconfig

[Randy Dunlap]

On Mon, 27 Sep 2010 12:45:59 -0000 Thomas Gleixner wrote:

> The generic irq Kconfig options are copied around all archs. Provide a
> generic Kconfig file which can be included.
> 
> Signed-off-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
> ---
>  kernel/irq/Kconfig |   49 +++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 49 insertions(+)
> 
> Index: linux-2.6-tip/kernel/irq/Kconfig
> ===================================================================
> --- /dev/null
> +++ linux-2.6-tip/kernel/irq/Kconfig
> @@ -0,0 +1,49 @@
> +#
> +# Interrupt subsystem related configuration options
> +#
> +
> +menu "Interrupt handling subsystem"
> +
> +config GENERIC_HARDIRQS
> +	def_bool y
> +
> +config GENERIC_HARDIRQS_NO__DO_IRQ
> +       def_bool y
> +
> +# Options selectable by the architecture code
> +config HAVE_SPARSE_IRQ
> +       def_bool n
> +
> +config GENERIC_IRQ_PROBE
> +	def_bool n
> +
> +config GENERIC_PENDING_IRQ
> +	def_bool n
> +
> +if SPARSE_IRQ && NUMA
> +config NUMA_IRQ_DESC
> +	def_bool n
> +endif
> +
> +config AUTO_IRQ_AFFINITY
> +       def_bool n
> +
> +config IRQ_PER_CPU
> +       def_bool n
> +
> +config HARDIRQS_SW_RESEND
> +       def_bool n
> +
> +config SPARSE_IRQ
> +	bool "Support sparse irq numbering"
> +	depends on HAVE_SPARSE_IRQ
> +	---help---
> +	  This enables support for sparse irqs. This is useful for distro
> +	  kernels that want to define a high CONFIG_NR_CPUS value but still
> +	  want to have low kernel memory footprint on smaller machines.
> +

I see that this is just moved from another location, but it would be good if
the "irq"s above could be like the one below (IRQ or IRQs).

> +	  ( 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.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/