From: "ito-yuichi@fujitsu.com" <ito-yuichi@fujitsu.com>
To: "ito-yuichi@fujitsu.com" <ito-yuichi@fujitsu.com>,
"maz@kernel.org" <maz@kernel.org>,
"sumit.garg@linaro.org" <sumit.garg@linaro.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"jason@lakedaemon.net" <jason@lakedaemon.net>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 0/2] Enable support IPI_CPU_CRASH_STOP to be pseudo-NMI
Date: Mon, 28 Sep 2020 02:43:10 +0000 [thread overview]
Message-ID: <OSAPR01MB42279E9BFA43419F49231ECE8F350@OSAPR01MB4227.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20200924044236.1245808-1-ito-yuichi@fujitsu.com>
Hi Marc, Sumit
I would appreciate if you have any advice on this patch.
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.
>
> This patch assumes Marc's latest IPIs patch-set. [1] It also uses some of
> Sumit's IPI patch set for NMI.[2]
>
> [1]
> https://lore.kernel.org/linux-arm-kernel/20200901144324.1071694-1-maz@ke
> rnel.org/
> [2]
> https://lore.kernel.org/linux-arm-kernel/1599830924-13990-3-git-send-email
> -sumit.garg@linaro.org/
>
> $ echo 1 > /proc/sys/kernel/panic_on_rcu_stal
> $ echo HARDLOCKUP > /sys/kernel/debug/provoke-crash/DIRECT
> : kernel panics and crash kernel boot
> : makedumpfile saves the system state at HARDLOCKUP in vmcore.
>
> crash utility:
> crash> bt
> PID: 3213 TASK: fffffd001adc5940 CPU: 8 COMMAND: "bash"
> #0 [fffffe0022fefcf0] lkdtm_HARDLOCKUP at fffffe0010888ab4
> #1 [fffffe0022fefd10] lkdtm_do_action at fffffe00108882bc
> #2 [fffffe0022fefd20] direct_entry at fffffe0010888720
> #3 [fffffe0022fefd70] full_proxy_write at fffffe001058cfe4
> #4 [fffffe0022fefdb0] vfs_write at fffffe00104a4c2c
> #5 [fffffe0022fefdf0] ksys_write at fffffe00104a4f0c
> #6 [fffffe0022fefe40] __arm64_sys_write at fffffe00104a4fbc
> #7 [fffffe0022fefe50] el0_svc_common.constprop.0 at fffffe0010159e38
> #8 [fffffe0022fefe80] do_el0_svc at fffffe0010159fa0
> #9 [fffffe0022fefe90] el0_svc at fffffe00101481d0
> #10 [fffffe0022fefea0] el0_sync_handler at fffffe00101484b4
> #11 [fffffe0022fefff0] el0_sync at fffffe0010142b7c
>
>
> Sumit Garg (1):
> irqchip/gic-v3: Enable support for SGIs to act as NMIs
>
> Yuichi Ito (1):
> Register IPI_CPU_CRASH_STOP IPI as pseudo-NMI
>
> arch/arm64/kernel/smp.c | 39
> ++++++++++++++++++++++++++++--------
> drivers/irqchip/irq-gic-v3.c | 13 ++++++++++--
> 2 files changed, 42 insertions(+), 10 deletions(-)
>
> --
> 2.25.1
next prev parent reply other threads:[~2020-09-28 2:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 4:42 [PATCH 0/2] Enable support IPI_CPU_CRASH_STOP to be pseudo-NMI Yuichi Ito
2020-09-24 4:42 ` [PATCH 1/2] irqchip/gic-v3: Enable support for SGIs to act as NMIs Yuichi Ito
2020-09-24 4:42 ` [PATCH 2/2] Register IPI_CPU_CRASH_STOP IPI as pseudo-NMI Yuichi Ito
2020-09-28 2:43 ` ito-yuichi [this message]
2020-09-28 8:59 ` [PATCH 0/2] Enable support IPI_CPU_CRASH_STOP to be pseudo-NMI Marc Zyngier
2020-09-29 5:50 ` ito-yuichi
2020-09-29 10:54 ` Marc Zyngier
2020-09-30 8:51 ` ito-yuichi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OSAPR01MB42279E9BFA43419F49231ECE8F350@OSAPR01MB4227.jpnprd01.prod.outlook.com \
--to=ito-yuichi@fujitsu.com \
--cc=catalin.marinas@arm.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=sumit.garg@linaro.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).