]> git.proxmox.com Git - mirror_ubuntu-bionic-kernel.git/blame - lib/Kconfig.kgdb
block: add kblockd_schedule_delayed_work_on()
[mirror_ubuntu-bionic-kernel.git] / lib / Kconfig.kgdb
CommitLineData
dc7d5527 1
e024cbd2
JE
2config HAVE_ARCH_KGDB
3 bool
4
dc7d5527 5menuconfig KGDB
dcc78711 6 bool "KGDB: kernel debugger"
dc7d5527 7 depends on HAVE_ARCH_KGDB
525c1f92 8 depends on DEBUG_KERNEL
dc7d5527
JW
9 help
10 If you say Y here, it will be possible to remotely debug the
5f5ddfb3
JW
11 kernel using gdb. It is recommended but not required, that
12 you also turn on the kernel config option
13 CONFIG_FRAME_POINTER to aid in producing more reliable stack
14 backtraces in the external debugger. Documentation of
15 kernel debugger is available at http://kgdb.sourceforge.net
16 as well as in DocBook form in Documentation/DocBook/. If
17 unsure, say N.
dc7d5527 18
e024cbd2 19if KGDB
dc7d5527
JW
20
21config KGDB_SERIAL_CONSOLE
22 tristate "KGDB: use kgdb over the serial console"
dc7d5527
JW
23 select CONSOLE_POLL
24 select MAGIC_SYSRQ
4f73bc4d 25 depends on TTY
dc7d5527
JW
26 default y
27 help
28 Share a serial console with kgdb. Sysrq-g must be used
29 to break in initially.
e8d31c20
JW
30
31config KGDB_TESTS
32 bool "KGDB: internal test suite"
e8d31c20
JW
33 default n
34 help
35 This is a kgdb I/O module specifically designed to test
36 kgdb's internal functions. This kgdb I/O module is
37 intended to for the development of new kgdb stubs
38 as well as regression testing the kgdb internals.
39 See the drivers/misc/kgdbts.c for the details about
40 the tests. The most basic of this I/O module is to boot
41 a kernel boot arguments "kgdbwait kgdbts=V1F100"
974460c5
JW
42
43config KGDB_TESTS_ON_BOOT
44 bool "KGDB: Run tests on boot"
45 depends on KGDB_TESTS
46 default n
47 help
48 Run the kgdb tests on boot up automatically without the need
49 to pass in a kernel parameter
50
51config KGDB_TESTS_BOOT_STRING
52 string "KGDB: which internal kgdb tests to run"
53 depends on KGDB_TESTS_ON_BOOT
54 default "V1F100"
55 help
56 This is the command string to send the kgdb test suite on
57 boot. See the drivers/misc/kgdbts.c for detailed
58 information about other strings you could use beyond the
59 default of V1F100.
e024cbd2 60
f503b5ae
JW
61config KGDB_LOW_LEVEL_TRAP
62 bool "KGDB: Allow debugging with traps in notifiers"
5dd11d5d 63 depends on X86 || MIPS
f503b5ae
JW
64 default n
65 help
66 This will add an extra call back to kgdb for the breakpoint
278cee05
MI
67 exception handler which will allow kgdb to step through a
68 notify handler.
f503b5ae 69
dcc78711
JW
70config KGDB_KDB
71 bool "KGDB_KDB: include kdb frontend for kgdb"
72 default n
73 help
74 KDB frontend for kernel
75
ada64e4c
JW
76config KDB_KEYBOARD
77 bool "KGDB_KDB: keyboard as input device"
78 depends on VT && KGDB_KDB
79 default n
80 help
81 KDB can use a PS/2 type keyboard for an input device
82
3b0eb71e
RO
83config KDB_CONTINUE_CATASTROPHIC
84 int "KDB: continue after catastrophic errors"
85 depends on KGDB_KDB
86 default "0"
87 help
88 This integer controls the behaviour of kdb when the kernel gets a
89 catastrophic error, i.e. for a panic or oops.
90 When KDB is active and a catastrophic error occurs, nothing extra
91 will happen until you type 'go'.
92 CONFIG_KDB_CONTINUE_CATASTROPHIC == 0 (default). The first time
93 you type 'go', you will be warned by kdb. The secend time you type
94 'go', KDB tries to continue. No guarantees that the
95 kernel is still usable in this situation.
96 CONFIG_KDB_CONTINUE_CATASTROPHIC == 1. KDB tries to continue.
97 No guarantees that the kernel is still usable in this situation.
98 CONFIG_KDB_CONTINUE_CATASTROPHIC == 2. KDB forces a reboot.
99 If you are not sure, say 0.
100
e024cbd2 101endif # KGDB