Re: [resend-without-rfc] powernv/kdump: Fix cases where the kdump kernel can get HMI's

2017-12-08 Thread Nicholas Piggin
On Fri, 08 Dec 2017 22:46:49 +1100 Michael Ellerman wrote: > Nicholas Piggin writes: > > > On Fri, 8 Dec 2017 14:35:33 +1100 > > Balbir Singh wrote: > > > >> Certain HMI's such as malfunction error propagate through > >> all threads/core on the system. If a thread was offline > >> prior to

Re: [resend-without-rfc] powernv/kdump: Fix cases where the kdump kernel can get HMI's

2017-12-08 Thread Michael Ellerman
Nicholas Piggin writes: > On Fri, 8 Dec 2017 14:35:33 +1100 > Balbir Singh wrote: > >> Certain HMI's such as malfunction error propagate through >> all threads/core on the system. If a thread was offline >> prior to us crashing the system and jumping to the kdump >> kernel, bad things happen wh

Re: [resend-without-rfc] powernv/kdump: Fix cases where the kdump kernel can get HMI's

2017-12-07 Thread Nicholas Piggin
On Fri, 8 Dec 2017 14:35:33 +1100 Balbir Singh wrote: > Certain HMI's such as malfunction error propagate through > all threads/core on the system. If a thread was offline > prior to us crashing the system and jumping to the kdump > kernel, bad things happen when it wakes up due to an HMI > in t

[resend-without-rfc] powernv/kdump: Fix cases where the kdump kernel can get HMI's

2017-12-07 Thread Balbir Singh
Certain HMI's such as malfunction error propagate through all threads/core on the system. If a thread was offline prior to us crashing the system and jumping to the kdump kernel, bad things happen when it wakes up due to an HMI in the kdump kernel. There are several possible ways to solve this pro