Re: [PATCH v3 3/3] powernv/kdump: Fix cases where the kdump kernel can get HMI's

2017-12-14 Thread Nicholas Piggin
On Fri, 15 Dec 2017 14:34:03 +1100 Balbir Singh wrote: > On Fri, Dec 15, 2017 at 2:10 PM, Nicholas Piggin wrote: > > On Fri, 15 Dec 2017 12:27:40 +1100 > > Balbir Singh wrote: > > But then you still need an explicit kdump check

Re: [PATCH v3 3/3] powernv/kdump: Fix cases where the kdump kernel can get HMI's

2017-12-14 Thread Balbir Singh
On Fri, Dec 15, 2017 at 2:10 PM, Nicholas Piggin wrote: > On Fri, 15 Dec 2017 12:27:40 +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

Re: [PATCH v3 3/3] powernv/kdump: Fix cases where the kdump kernel can get HMI's

2017-12-14 Thread Nicholas Piggin
On Fri, 15 Dec 2017 12:27:40 +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

[PATCH v3 3/3] powernv/kdump: Fix cases where the kdump kernel can get HMI's

2017-12-14 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