summaryrefslogtreecommitdiffstats
path: root/kernel/kgdb.c
diff options
context:
space:
mode:
authorJan Kiszka <jan.kiszka@siemens.com>2008-10-06 13:50:59 -0500
committerJason Wessel <jason.wessel@windriver.com>2008-10-06 13:50:59 -0500
commite85ceae9102f6e3c1d707e7ac88fa48d252e9cfa (patch)
treec0ea708310452d42b35ea3eb422654fc4fd1f778 /kernel/kgdb.c
parentfec6ed1d1f9b78a6acb4a3eb2c46c812ac2e96f0 (diff)
downloadop-kernel-dev-e85ceae9102f6e3c1d707e7ac88fa48d252e9cfa.zip
op-kernel-dev-e85ceae9102f6e3c1d707e7ac88fa48d252e9cfa.tar.gz
kgdb, x86: Avoid invoking kgdb_nmicallback twice per NMI
Stress-testing KVM's latest NMI support with kgdbts inside an SMP guest, I came across spurious unhandled NMIs while running the singlestep test. Looking closer at the code path each NMI takes when KGDB is enabled, I noticed that kgdb_nmicallback is called twice per event: One time via DIE_NMI_IPI notification, the second time on DIE_NMI. Removing the first invocation cures the unhandled NMIs here. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Diffstat (limited to 'kernel/kgdb.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud