forked from Minki/linux
kernel-hacking: move Oops into 'Lockups and Hangs'
They are similar options so place them together. Link: http://lkml.kernel.org/r/20190909144453.3520-6-changbin.du@gmail.com Signed-off-by: Changbin Du <changbin.du@gmail.com> Acked-by: Randy Dunlap <rdunlap@infradead.org> Tested-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
09a7495258
commit
f43a289df6
@ -773,7 +773,35 @@ config DEBUG_SHIRQ
|
|||||||
Drivers ought to be able to handle interrupts coming in at those
|
Drivers ought to be able to handle interrupts coming in at those
|
||||||
points; some don't and need to be caught.
|
points; some don't and need to be caught.
|
||||||
|
|
||||||
menu "Debug Lockups and Hangs"
|
menu "Debug Oops, Lockups and Hangs"
|
||||||
|
|
||||||
|
config PANIC_ON_OOPS
|
||||||
|
bool "Panic on Oops"
|
||||||
|
help
|
||||||
|
Say Y here to enable the kernel to panic when it oopses. This
|
||||||
|
has the same effect as setting oops=panic on the kernel command
|
||||||
|
line.
|
||||||
|
|
||||||
|
This feature is useful to ensure that the kernel does not do
|
||||||
|
anything erroneous after an oops which could result in data
|
||||||
|
corruption or other issues.
|
||||||
|
|
||||||
|
Say N if unsure.
|
||||||
|
|
||||||
|
config PANIC_ON_OOPS_VALUE
|
||||||
|
int
|
||||||
|
range 0 1
|
||||||
|
default 0 if !PANIC_ON_OOPS
|
||||||
|
default 1 if PANIC_ON_OOPS
|
||||||
|
|
||||||
|
config PANIC_TIMEOUT
|
||||||
|
int "panic timeout"
|
||||||
|
default 0
|
||||||
|
help
|
||||||
|
Set the timeout value (in seconds) until a reboot occurs when the
|
||||||
|
the kernel panics. If n = 0, then we wait forever. A timeout
|
||||||
|
value n > 0 will wait n seconds before rebooting, while a timeout
|
||||||
|
value n < 0 will reboot immediately.
|
||||||
|
|
||||||
config LOCKUP_DETECTOR
|
config LOCKUP_DETECTOR
|
||||||
bool
|
bool
|
||||||
@ -931,34 +959,6 @@ config WQ_WATCHDOG
|
|||||||
|
|
||||||
endmenu # "Debug lockups and hangs"
|
endmenu # "Debug lockups and hangs"
|
||||||
|
|
||||||
config PANIC_ON_OOPS
|
|
||||||
bool "Panic on Oops"
|
|
||||||
help
|
|
||||||
Say Y here to enable the kernel to panic when it oopses. This
|
|
||||||
has the same effect as setting oops=panic on the kernel command
|
|
||||||
line.
|
|
||||||
|
|
||||||
This feature is useful to ensure that the kernel does not do
|
|
||||||
anything erroneous after an oops which could result in data
|
|
||||||
corruption or other issues.
|
|
||||||
|
|
||||||
Say N if unsure.
|
|
||||||
|
|
||||||
config PANIC_ON_OOPS_VALUE
|
|
||||||
int
|
|
||||||
range 0 1
|
|
||||||
default 0 if !PANIC_ON_OOPS
|
|
||||||
default 1 if PANIC_ON_OOPS
|
|
||||||
|
|
||||||
config PANIC_TIMEOUT
|
|
||||||
int "panic timeout"
|
|
||||||
default 0
|
|
||||||
help
|
|
||||||
Set the timeout value (in seconds) until a reboot occurs when the
|
|
||||||
the kernel panics. If n = 0, then we wait forever. A timeout
|
|
||||||
value n > 0 will wait n seconds before rebooting, while a timeout
|
|
||||||
value n < 0 will reboot immediately.
|
|
||||||
|
|
||||||
config SCHED_DEBUG
|
config SCHED_DEBUG
|
||||||
bool "Collect scheduler debugging info"
|
bool "Collect scheduler debugging info"
|
||||||
depends on DEBUG_KERNEL && PROC_FS
|
depends on DEBUG_KERNEL && PROC_FS
|
||||||
|
Loading…
Reference in New Issue
Block a user