Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752847AbYKLNgb (ORCPT ); Wed, 12 Nov 2008 08:36:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752190AbYKLNfs (ORCPT ); Wed, 12 Nov 2008 08:35:48 -0500 Received: from mx2.redhat.com ([66.187.237.31]:45162 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752005AbYKLNfp (ORCPT ); Wed, 12 Nov 2008 08:35:45 -0500 From: Eduardo Habkost To: Ingo Molnar Cc: Avi Kivity , "Eric W. Biederman" , Simon Horman , Andrew Morton , Vivek Goyal , Haren Myneni , Andrey Borzenkov , "Rafael J. Wysocki" , kexec@lists.infradead.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Eduardo Habkost Subject: [PATCH 8/8] x86: Disable IRQs before doing anything on nmi_shootdown_cpus() Date: Wed, 12 Nov 2008 11:34:44 -0200 Message-Id: <1226496884-24628-9-git-send-email-ehabkost@redhat.com> In-Reply-To: <1226496884-24628-1-git-send-email-ehabkost@redhat.com> References: <1226496884-24628-1-git-send-email-ehabkost@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 938 Lines: 28 We need to know on which CPU we are running on, and we don't want to be preempted while doing this. Signed-off-by: Eduardo Habkost --- arch/x86/kernel/reboot.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/arch/x86/kernel/reboot.c b/arch/x86/kernel/reboot.c index d0c9c77..c495687 100644 --- a/arch/x86/kernel/reboot.c +++ b/arch/x86/kernel/reboot.c @@ -582,6 +582,7 @@ static struct notifier_block crash_nmi_nb = { void nmi_shootdown_cpus(nmi_shootdown_cb callback) { unsigned long msecs; + local_irq_disable(); /* Make a note of crashing cpu. Will be used in NMI callback.*/ crashing_cpu = safe_smp_processor_id(); -- 1.5.5.GIT -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/