2010-09-27 12:45:59 +00:00
config HAVE_GENERIC_HARDIRQS
2011-02-17 13:39:05 +00:00
bool
2010-09-27 12:45:59 +00:00
if HAVE_GENERIC_HARDIRQS
menu "IRQ subsystem"
#
# Interrupt subsystem related configuration options
#
config GENERIC_HARDIRQS
def_bool y
2010-10-01 15:17:14 +02:00
# Select this to disable the deprecated stuff
config GENERIC_HARDIRQS_NO_DEPRECATED
2011-02-17 13:39:05 +00:00
bool
2010-10-01 15:17:14 +02:00
2011-02-07 21:48:49 +01:00
config GENERIC_HARDIRQS_NO_COMPAT
2011-02-17 13:39:05 +00:00
bool
2011-02-07 21:48:49 +01:00
2010-09-27 12:45:59 +00:00
# Options selectable by the architecture code
config HAVE_SPARSE_IRQ
2011-02-17 13:39:05 +00:00
bool
2010-09-27 12:45:59 +00:00
config GENERIC_IRQ_PROBE
2011-02-17 13:39:05 +00:00
bool
2010-09-27 12:45:59 +00:00
2010-12-16 17:21:47 +01:00
config GENERIC_IRQ_SHOW
2011-02-17 13:39:05 +00:00
bool
2010-12-16 17:21:47 +01:00
2010-09-27 12:45:59 +00:00
config GENERIC_PENDING_IRQ
2011-02-17 13:39:05 +00:00
bool
2010-09-27 12:45:59 +00:00
config AUTO_IRQ_AFFINITY
2011-02-17 13:39:05 +00:00
bool
2010-09-27 12:45:59 +00:00
config HARDIRQS_SW_RESEND
2011-02-17 13:39:05 +00:00
bool
2010-09-27 12:45:59 +00:00
2011-02-10 15:14:20 +01:00
config IRQ_PREFLOW_FASTEOI
2011-02-17 13:39:05 +00:00
bool
2011-02-10 15:14:20 +01:00
2010-09-27 12:45:59 +00:00
config SPARSE_IRQ
bool "Support sparse irq numbering"
depends on HAVE_SPARSE_IRQ
---help---
Sparse irq numbering 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.
( 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.
endmenu
endif
