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 <daniel.thompson@linaro.org>
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>

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

..

kdb

kdb: Remove stack dump when entering kgdb due to NMI

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

debug_core.c

kdb: Fix off by one error in kdb_cpu()

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

debug_core.h

kgdb/kdb: Fix no KDB config problem

2014-01-25 08:55:09 +01:00

gdbstub.c

KGDB/KDB fixes and cleanups

2013-03-02 08:31:39 -08:00

Makefile

kdb: core for kgdb back end (1 of 2)

2010-05-20 21:04:20 -05:00