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

2017-12-14 Thread Balbir Singh
On Fri, Dec 15, 2017 at 12:32 AM, Nicholas Piggin wrote: > On Thu, 14 Dec 2017 23:16:26 +1100 > Balbir Singh wrote: > >> On Thu, Dec 14, 2017 at 12:51 PM, Nicholas Piggin wrote: > > >> >> I can't call smp_send_nmi_ipi due to the nmi_ipi_busy_count and >> >> I'm worried about calling a stale nmi_

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

2017-12-14 Thread Nicholas Piggin
On Thu, 14 Dec 2017 23:16:26 +1100 Balbir Singh wrote: > On Thu, Dec 14, 2017 at 12:51 PM, Nicholas Piggin wrote: > >> I can't call smp_send_nmi_ipi due to the nmi_ipi_busy_count and > >> I'm worried about calling a stale nmi_ipi_function via the > >> system_reset_exception path, if we are OK

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

2017-12-14 Thread Balbir Singh
On Thu, Dec 14, 2017 at 12:51 PM, Nicholas Piggin wrote: > On Thu, 14 Dec 2017 11:12:13 +1100 > Balbir Singh wrote: > >> On Wed, 13 Dec 2017 20:51:01 +1000 >> Nicholas Piggin wrote: >> >> > This is looking pretty nice now... >> > >> > On Wed, 13 Dec 2017 19:08:28 +1100 >> > Balbir Singh wrote:

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

2017-12-13 Thread Nicholas Piggin
On Thu, 14 Dec 2017 11:12:13 +1100 Balbir Singh wrote: > On Wed, 13 Dec 2017 20:51:01 +1000 > Nicholas Piggin wrote: > > > This is looking pretty nice now... > > > > On Wed, 13 Dec 2017 19:08:28 +1100 > > Balbir Singh wrote: > > > > > @@ -543,7 +543,25 @@ void smp_send_debugger_break(void)

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

2017-12-13 Thread Balbir Singh
On Wed, 13 Dec 2017 20:51:01 +1000 Nicholas Piggin wrote: > This is looking pretty nice now... > > On Wed, 13 Dec 2017 19:08:28 +1100 > Balbir Singh wrote: > > > @@ -543,7 +543,25 @@ void smp_send_debugger_break(void) > > #ifdef CONFIG_KEXEC_CORE > > void crash_send_ipi(void (*crash_ipi_call

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

2017-12-13 Thread Nicholas Piggin
This is looking pretty nice now... On Wed, 13 Dec 2017 19:08:28 +1100 Balbir Singh wrote: > @@ -543,7 +543,25 @@ void smp_send_debugger_break(void) > #ifdef CONFIG_KEXEC_CORE > void crash_send_ipi(void (*crash_ipi_callback)(struct pt_regs *)) > { > + int cpu; > + > smp_send_nmi_ipi(

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

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