hollalinux
/
linux-sg2042
mirror of https://github.com/sophgo/linux-riscv.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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>
This commit is contained in:
Daniel Thompson 2014-11-06 15:32:13 +00:00 committed by Jason Wessel
parent f7d4ca8bbf
commit 5454388113
1 changed files with 0 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
kernel/debug/kdb/kdb_main.c
View File

@ -1247,7 +1247,6 @@ static int kdb_local(kdb_reason_t reason, int error, struct pt_regs *regs,
kdb_printf("due to NonMaskable Interrupt @ " kdb_printf("due to NonMaskable Interrupt @ "
kdb_machreg_fmt "\n", kdb_machreg_fmt "\n",
instruction_pointer(regs)); instruction_pointer(regs));
kdb_dumpregs(regs);
break; break;
case KDB_REASON_SSTEP: case KDB_REASON_SSTEP:
case KDB_REASON_BREAK: case KDB_REASON_BREAK: