Daniel Thompson 5454388113 kdb: Remove stack dump when entering kgdb due to NMI ...

Issuing a stack dump feels ergonomically wrong when entering due to NMI.

Entering due to NMI is normally a reaction to a user request, either the
NMI button on a server or a "magic knock" on a UART. Therefore the
backtrace behaviour on entry due to NMI should be like SysRq-g (no stack
dump) rather than like oops.

Note also that the stack dump does not offer any information that
cannot be trivial retrieved using the 'bt' command.

Signed-off-by: Daniel Thompson <[email protected]>
Signed-off-by: Jason Wessel <[email protected]>

2015-02-19 12:39:02 -06:00

..

.gitignore

…

kdb_bp.c

kdb: Categorize kdb commands (similar to SysRq categorization)

2014-11-11 09:31:52 -06:00

kdb_bt.c

kernel/printk: use symbolic defines for console loglevels

2014-06-04 16:54:17 -07:00

kdb_cmds

kdb: cleanup unused variables missed in the original kdb merge

2011-08-01 13:23:58 -05:00

kdb_debugger.c

kgdb: timeout if secondary CPUs ignore the roundup

2014-11-11 09:31:53 -06:00

kdb_io.c

kdb: Avoid printing KERN_ levels to consoles

2015-02-19 12:39:02 -06:00

kdb_keyboard.c

KDB: Fix usability issues relating to the 'enter' key.

2012-03-22 15:07:15 -05:00

kdb_main.c

kdb: Remove stack dump when entering kgdb due to NMI

2015-02-19 12:39:02 -06:00

kdb_private.h

kdb: Rename kdb_repeat_t to kdb_cmdflags_t, cmd_repeat to cmd_flags

2014-11-11 09:31:51 -06:00

kdb_support.c

kdb: remove the second argument of k[un]map_atomic()

2012-03-20 21:48:26 +08:00

Makefile

…