[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OSAPR01MB4227204DB45A285761B520998F320@OSAPR01MB4227.jpnprd01.prod.outlook.com>
Date: Tue, 29 Sep 2020 05:50:04 +0000
From: "ito-yuichi@...itsu.com" <ito-yuichi@...itsu.com>
To: 'Marc Zyngier' <maz@...nel.org>
CC: "sumit.garg@...aro.org" <sumit.garg@...aro.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"jason@...edaemon.net" <jason@...edaemon.net>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"will@...nel.org" <will@...nel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 0/2] Enable support IPI_CPU_CRASH_STOP to be pseudo-NMI
Hi Marc
Thank you for your reply.
> On 2020-09-28 03:43, ito-yuichi@...itsu.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
Powered by blists - more mailing lists