lkml.org 
[lkml]   [2020]   [Sep]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 0/2] Enable support IPI_CPU_CRASH_STOP to be pseudo-NMI
On 2020-09-28 03:43, ito-yuichi@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).

>
> Yuichi Ito
>
>> -----Original Message-----
>> From: Yuichi Ito <ito-yuichi@fujitsu.com>
>> Sent: Thursday, September 24, 2020 1:43 PM
>> To: maz@kernel.org; sumit.garg@linaro.org; tglx@linutronix.de;
>> jason@lakedaemon.net; catalin.marinas@arm.com; will@kernel.org
>> Cc: linux-arm-kernel@lists.infradead.org;
>> linux-kernel@vger.kernel.org; Ito,
>> Yuichi/伊藤 有一 <ito-yuichi@fujitsu.com>
>> 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...

\
 
 \ /
  Last update: 2020-09-28 11:00    [W:0.066 / U:29.912 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site