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

[ito-yuichi at fujitsu.com]

Hi Marc

Thank you for your reply.

> On 2020-09-28 03:43, ito-yuichi at fujitsu.com 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).
> 

I understand it.
Please let me know if there is anything I can do.
I sincerely hope that your patches will be merged into the mainline.

> >
> > Yuichi Ito
> >
> >> 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.

I tried it with ThunderX CN8890.
If you tell me steps to reproduce the problem of TX2, I will investigate it with TX as well.

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

Thank you and best regards,

Yuichi Ito