1# Select this to activate the generic irq options below 2config HAVE_GENERIC_HARDIRQS 3 bool 4 5if HAVE_GENERIC_HARDIRQS 6menu "IRQ subsystem" 7# 8# Interrupt subsystem related configuration options 9# 10config GENERIC_HARDIRQS 11 def_bool y 12 13# Select this to disable the deprecated stuff 14config GENERIC_HARDIRQS_NO_DEPRECATED 15 bool 16 17config GENERIC_HARDIRQS_NO_COMPAT 18 bool 19 20# Options selectable by the architecture code 21 22# Make sparse irq Kconfig switch below available 23config HAVE_SPARSE_IRQ 24 bool 25 26# Enable the generic irq autoprobe mechanism 27config GENERIC_IRQ_PROBE 28 bool 29 30# Use the generic /proc/interrupts implementation 31config GENERIC_IRQ_SHOW 32 bool 33 34# Support for delayed migration from interrupt context 35config GENERIC_PENDING_IRQ 36 bool 37 38# Alpha specific irq affinity mechanism 39config AUTO_IRQ_AFFINITY 40 bool 41 42# Tasklet based software resend for pending interrupts on enable_irq() 43config HARDIRQS_SW_RESEND 44 bool 45 46# Preflow handler support for fasteoi (sparc64) 47config IRQ_PREFLOW_FASTEOI 48 bool 49 50# Support forced irq threading 51config IRQ_FORCED_THREADING 52 bool 53 54config SPARSE_IRQ 55 bool "Support sparse irq numbering" 56 depends on HAVE_SPARSE_IRQ 57 ---help--- 58 59 Sparse irq numbering is useful for distro kernels that want 60 to define a high CONFIG_NR_CPUS value but still want to have 61 low kernel memory footprint on smaller machines. 62 63 ( Sparse irqs can also be beneficial on NUMA boxes, as they spread 64 out the interrupt descriptors in a more NUMA-friendly way. ) 65 66 If you don't know what to do here, say N. 67 68endmenu 69endif 70