Re: [PATCH 0/2] Enable support IPI_CPU_CRASH_STOP to be pseudo-NMI

[Marc Zyngier]

On 2020-09-28 03:43, ito-yuichi@xxxxxxxxxxx wrote:
> Hi Marc, Sumit
>
> I would appreciate if you have any advice on this patch.

I haven't had a chance to look into it, as I'm not even sure I'll
take the core series in the first place (there are outstanding
regressions I can't reproduce, let alone fix them).

> Yuichi Ito
>
> > -----Original Message-----
> > From: Yuichi Ito <ito-yuichi@xxxxxxxxxxx>
> > Sent: Thursday, September 24, 2020 1:43 PM
> > To: maz@xxxxxxxxxx; sumit.garg@xxxxxxxxxx; tglx@xxxxxxxxxxxxx;
> > jason@xxxxxxxxxxxxxx; catalin.marinas@xxxxxxx; will@xxxxxxxxxx
> > Cc: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; 
> > linux-kernel@xxxxxxxxxxxxxxx; Ito,
> > Yuichi/伊藤 有一 <ito-yuichi@xxxxxxxxxxx>
> > Subject: [PATCH 0/2] Enable support IPI_CPU_CRASH_STOP to be
> > pseudo-NMI
> >
> > Enable support IPI_CPU_CRASH_STOP to be pseudo-NMI
> >
> > This patchset enables IPI_CPU_CRASH_STOP IPI to be pseudo-NMI.
> > This allows kdump to collect system information even when the CPU is 
> > in a
> > HARDLOCKUP state.
> >
> > Only IPI_CPU_CRASH_STOP uses NMI and the other IPIs remain normal
> > IRQs.
> >
> > The patch has been tested on ThunderX.

Which ThunderX? TX2 (at least the incarnation I used in the past) wasn't
able to correctly deal with priorities.

        M.
--
Jazz is not dead. It just smells funny...