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 at intel.com> -Tony
