summaryrefslogtreecommitdiffstats
path: root/arch/x86/kernel/tlb_uv.c
diff options
context:
space:
mode:
authorCliff Wickman2010-07-21 01:09:05 +0200
committerH. Peter Anvin2010-07-21 20:33:27 +0200
commit5edd19af18a36a4e22c570b1b969179e0ca1fe4c (patch)
treead4c52f24218c1358d8e8ea51d2ce23a20c37d68 /arch/x86/kernel/tlb_uv.c
parentx86, UV: Initialize BAU MMRs only on hubs with cpus (diff)
downloadkernel-qcow2-linux-5edd19af18a36a4e22c570b1b969179e0ca1fe4c.tar.gz
kernel-qcow2-linux-5edd19af18a36a4e22c570b1b969179e0ca1fe4c.tar.xz
kernel-qcow2-linux-5edd19af18a36a4e22c570b1b969179e0ca1fe4c.zip
x86, UV: Make kdump avoid stack dumps
UV NMI callback's should not write stack dumps when a kdump is to be written. When invoking the crash kernel to write a dump, kdump_nmi_shootdown_cpus() uses NMI's to get all the cpu's to save their register context and halt. But the NMI interrupt handler runs a callback list. This patch sets a flag to prevent any of those callbacks from interfering with the halt of the cpu. For UV, which currently has the only callback to which this is relevant, the uv_handle_nmi() callback should not do dumping of stacks. The 'in_crash_kexec' flag is defined as an extern in kdebug.h firstly because x2apic_uv_x.c includes it. Secondly because some future callback might need the flag to know that it should not enter the debugger. (Such a scenario was in fact present in the 2.6.32 kernel, SuSE distribution, where a call to kdb needed to be avoided.) Signed-off-by: Cliff Wickman <cpw@sgi.com> LKML-Reference: <E1ObLvt-0005UZ-Va@eag09.americas.sgi.com> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Diffstat (limited to 'arch/x86/kernel/tlb_uv.c')
0 files changed, 0 insertions, 0 deletions