| Kconfig.debug (1dbbb6077426f8ce63d6a59c5ac6613e1689cbde) | Kconfig.debug (85218827cc4ca900867807f19345418164ffc108) |
|---|---|
| 1menu "Kernel hacking" 2 3source "lib/Kconfig.debug" 4 5config DEBUG_STACKOVERFLOW 6 bool "Check for stack overflows" 7 depends on DEBUG_KERNEL 8 help --- 104 unchanged lines hidden (view full) --- 113 default y 114 help 115 Include support for disassembling in xmon. You probably want 116 to say Y here, unless you're building for a memory-constrained 117 system. 118 119config IRQSTACKS 120 bool "Use separate kernel stacks when processing interrupts" | 1menu "Kernel hacking" 2 3source "lib/Kconfig.debug" 4 5config DEBUG_STACKOVERFLOW 6 bool "Check for stack overflows" 7 depends on DEBUG_KERNEL 8 help --- 104 unchanged lines hidden (view full) --- 113 default y 114 help 115 Include support for disassembling in xmon. You probably want 116 to say Y here, unless you're building for a memory-constrained 117 system. 118 119config IRQSTACKS 120 bool "Use separate kernel stacks when processing interrupts" |
| 121 depends on PPC64 | |
| 122 help 123 If you say Y here the kernel will use separate kernel stacks 124 for handling hard and soft interrupts. This can help avoid 125 overflowing the process kernel stacks. 126 127config VIRQ_DEBUG 128 bool "Expose hardware/virtual IRQ mapping via debugfs" 129 depends on DEBUG_FS && PPC_MERGE --- 154 unchanged lines hidden --- | 121 help 122 If you say Y here the kernel will use separate kernel stacks 123 for handling hard and soft interrupts. This can help avoid 124 overflowing the process kernel stacks. 125 126config VIRQ_DEBUG 127 bool "Expose hardware/virtual IRQ mapping via debugfs" 128 depends on DEBUG_FS && PPC_MERGE --- 154 unchanged lines hidden --- |