[PATCH 0/5] More NMI IPI enablement work · Nicholas Piggin <npiggin@gmail.com> · 2017-09-18
[PATCH 1/5] powerpc/watchdog: do not panic from locked CPU's IPI handler · Nicholas Piggin <npiggin@gmail.com> · 2017-09-18
[PATCH 2/5] powerpc/watchdog: do not backtrace locked CPUs twice if allcpus backtrace is enabled · Nicholas Piggin <npiggin@gmail.com> · 2017-09-18
[PATCH 3/5] powerpc/watchdog: do not trigger SMP crash from touch_nmi_watchdog · Nicholas Piggin <npiggin@gmail.com> · 2017-09-18
[PATCH 4/5] powerpc/xmon: avoid tripping SMP hardlockup watchdog · Nicholas Piggin <npiggin@gmail.com> · 2017-09-18
[PATCH 5/5] powerpc/powernv: implement NMI IPI with OPAL_SIGNAL_SYSTEM_RESET · Nicholas Piggin <npiggin@gmail.com> · 2017-09-18
Re: [PATCH 0/5] More NMI IPI enablement work · Michael Ellerman <mpe@ellerman.id.au> · 2017-09-21
Re: [PATCH 0/5] More NMI IPI enablement work · Nicholas Piggin <npiggin@gmail.com> · 2017-09-21

Re: [PATCH 0/5] More NMI IPI enablement work

From: Michael Ellerman <mpe@ellerman.id.au>
Date: 2017-09-21 11:10:43

Nicholas Piggin [off-list ref] writes:

Hi,

Here is the NMI IPI enablement for powernv, which requires
supported firmware and hardware:

https://lists.ozlabs.org/pipermail/skiboot/2017-September/009111.html

And some preceeding patches that fix issues I ran into when
testing it.

Are any of these critical such that I should pick them up for 4.14 or
earlier?

cheers

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help