All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	mingo@redhat.com, Ingo Molnar <mingo@elte.hu>,
	tglx@linutronix.de
Subject: Re: [PATCH], issue EOI to APIC prior to calling crash_kexec in	die_nmi path
Date: Wed, 06 Feb 2008 14:56:22 -0800	[thread overview]
Message-ID: <47AA3B16.7000507@zytor.com> (raw)
In-Reply-To: <20080206224805.GD11886@redhat.com>

Vivek Goyal wrote:
> 
> I am wondering if interrupts are disabled on crashing cpu or if crashing
> cpu is inside die_nmi(), how would it stop/prevent delivery of NMI IPI to
> other cpus.
> 

I don't see how it would.

	-hpa

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, Neil Horman <nhorman@tuxdriver.com>,
	tglx@linutronix.de, mingo@redhat.com, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH], issue EOI to APIC prior to calling crash_kexec in	die_nmi path
Date: Wed, 06 Feb 2008 14:56:22 -0800	[thread overview]
Message-ID: <47AA3B16.7000507@zytor.com> (raw)
In-Reply-To: <20080206224805.GD11886@redhat.com>

Vivek Goyal wrote:
> 
> I am wondering if interrupts are disabled on crashing cpu or if crashing
> cpu is inside die_nmi(), how would it stop/prevent delivery of NMI IPI to
> other cpus.
> 

I don't see how it would.

	-hpa

  parent reply	other threads:[~2008-02-06 23:00 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 19:25 [PATCH], issue EOI to APIC prior to calling crash_kexec in die_nmi path Neil Horman
2008-02-06 19:25 ` Neil Horman
2008-02-06 19:40 ` Vivek Goyal
2008-02-06 19:40   ` Vivek Goyal
2008-02-06 20:12   ` Neil Horman
2008-02-06 20:12     ` Neil Horman
2008-02-06 20:21     ` H. Peter Anvin
2008-02-06 20:21       ` H. Peter Anvin
2008-02-06 21:04       ` Neil Horman
2008-02-06 21:04         ` Neil Horman
2008-02-06 20:35     ` Vivek Goyal
2008-02-06 20:35       ` Vivek Goyal
2008-02-06 22:00 ` Ingo Molnar
2008-02-06 22:00   ` Ingo Molnar
2008-02-06 22:48   ` Vivek Goyal
2008-02-06 22:48     ` Vivek Goyal
2008-02-06 22:53     ` Ingo Molnar
2008-02-06 22:53       ` Ingo Molnar
2008-02-06 22:56     ` H. Peter Anvin [this message]
2008-02-06 22:56       ` H. Peter Anvin
2008-02-06 23:36       ` Ingo Molnar
2008-02-06 23:36         ` Ingo Molnar
2008-02-06 23:50         ` Vivek Goyal
2008-02-06 23:50           ` Vivek Goyal
2008-02-07  0:31         ` Eric W. Biederman
2008-02-07  0:31           ` Eric W. Biederman
2008-02-07  0:39           ` Ingo Molnar
2008-02-07  0:39             ` Ingo Molnar
2008-02-07  1:30             ` Eric W. Biederman
2008-02-07  1:30               ` Eric W. Biederman
2008-02-07 12:17           ` Neil Horman
2008-02-07 12:17             ` Neil Horman
2008-02-07 12:24             ` Ingo Molnar
2008-02-07 12:24               ` Ingo Molnar
2008-02-07 20:37               ` Neil Horman
2008-02-07 20:37                 ` Neil Horman
2008-02-08 16:14               ` Neil Horman
2008-02-08 16:14                 ` Neil Horman
2008-02-08 16:45                 ` Vivek Goyal
2008-02-08 16:45                   ` Vivek Goyal
2008-02-08 17:26                   ` Neil Horman
2008-02-08 17:26                     ` Neil Horman
2008-02-12 21:08                   ` Neil Horman
2008-02-12 21:08                     ` Neil Horman
2008-02-15 14:02                     ` Eric W. Biederman
2008-02-15 14:02                       ` Eric W. Biederman
2008-02-20 14:57                     ` Neil Horman
2008-02-20 14:57                       ` Neil Horman
2008-02-08 16:54               ` Andi Kleen
2008-02-08 16:54                 ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47AA3B16.7000507@zytor.com \
    --to=hpa@zytor.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=nhorman@tuxdriver.com \
    --cc=tglx@linutronix.de \
    --cc=vgoyal@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.