kdb: Remove stack dump when entering kgdb due to NMI
authorDaniel Thompson <daniel.thompson@linaro.org>
Thu, 6 Nov 2014 15:32:13 +0000 (15:32 +0000)
committerJason Wessel <jason.wessel@windriver.com>
Thu, 19 Feb 2015 18:39:02 +0000 (12:39 -0600)
commit5454388113938d9592d6a6d5424469014da4ee86
tree0765c2a49d358edb97bd170f29dc90904e990b5b
parentf7d4ca8bbfda23b4f1eae9b6757ff64166b093d5
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>
kernel/debug/kdb/kdb_main.c