Re: [PATCH v4] x86/mce: Don't participate in rendezvous process once nmi_shootdown_cpus() was made

From	"Luck, Tony" <tony.luck@intel.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH v4] x86/mce: Don't participate in rendezvous process once nmi_shootdown_cpus() was made
Date	2017-03-06 19:40 +0100
Message-ID	<ti5I6-3Hy-9@gated-at.bofh.it> (permalink)
References	<te1MJ-1Qh-9@gated-at.bofh.it> <thZt0-7Fd-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Mon, Mar 06, 2017 at 12:16:54PM +0100, Borislav Petkov wrote:
> On Thu, Feb 23, 2017 at 09:36:52PM +0800, Xunlei Pang wrote:
> > We met an issue for kdump: after kdump kernel boots up,
> > and there comes a broadcasted mce in first kernel, the
> > other cpus remaining in first kernel will enter the old
> > mce handler of first kernel, then timeout and panic due
> > to MCE synchronization, finally reset the kdump cpus.
> > 
> > This patch lets cpus stay quiet after nmi_shootdown_cpus(),
> > so after kdump boots, cpus remaining in 1st kernel should
> > not do anything except clearing MCG_STATUS. This is useful
> > for kdump to let vmcore dumping perform as hard as it can.
> 
> Ok, I went and rewrote the text to make it more succinct, to the point
> and correct spelling and formatting.
> 
> Tony, ACK?

Yes. Looks good now.

Acked-by: Tony Luck <tony.luck@intel.com>

-Tony

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: [PATCH v4] x86/mce: Don't participate in rendezvous process once  nmi_shootdown_cpus() was made Borislav Petkov <bp@alien8.de> - 2017-03-06 13:00 +0100
  Re: [PATCH v4] x86/mce: Don't participate in rendezvous process once  nmi_shootdown_cpus() was made "Luck, Tony" <tony.luck@intel.com> - 2017-03-06 19:40 +0100

csiph-web