From: daniel.thompson@linaro.org (Daniel Thompson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm: Fix "NMI" backtrace for Inforce IFC6410
Date: Wed, 16 Dec 2015 17:08:05 +0000 [thread overview]
Message-ID: <1450285686-844-2-git-send-email-daniel.thompson@linaro.org> (raw)
In-Reply-To: <1450285686-844-1-git-send-email-daniel.thompson@linaro.org>
SysRq-L does not generate a backtrace from all CPUs when I test it
on my Inforce IFC6410 platform (Snapdragon 600). The stack dump code,
triggered by IPI_CPU_BACKTRACE, never runs on the other CPUs.
Eventually we hit the 10 second timeout and a subset of the expected
stack dumps on are shown on the console.
It is likely this is because SGI IDs 14 and 15 have been reserved for
use by secure world on this platform. For IFC6410 platform the code
works as expected when IPI_CPU_BACKTRACE is set to any value in the
interval 9..13.
Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
---
arch/arm/kernel/smp.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/kernel/smp.c b/arch/arm/kernel/smp.c
index b26361355dae..78205927fcd4 100644
--- a/arch/arm/kernel/smp.c
+++ b/arch/arm/kernel/smp.c
@@ -73,7 +73,8 @@ enum ipi_msg_type {
IPI_CPU_STOP,
IPI_IRQ_WORK,
IPI_COMPLETION,
- IPI_CPU_BACKTRACE = 15,
+ IPI_CPU_BACKTRACE = 13,
+ /* 14 and 15 are reserved; they do not work on some Krait CPUs */
};
static DECLARE_COMPLETION(cpu_running);
--
2.5.0
next prev parent reply other threads:[~2015-12-16 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 17:08 [PATCH 0/2] Fix NMI backtrace for Inforce IFC6410 Daniel Thompson
2015-12-16 17:08 ` Daniel Thompson [this message]
2015-12-18 8:58 ` [PATCH 1/2] arm: Fix "NMI" " Marc Zyngier
2015-12-16 17:08 ` [PATCH 2/2] irqchip/gic: Identify and report any reserved SGI IDs Daniel Thompson
2015-12-16 17:47 ` Marc Zyngier
2015-12-17 19:26 ` Daniel Thompson
2015-12-18 7:39 ` Marc Zyngier
2015-12-18 11:29 ` Daniel Thompson
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=1450285686-844-2-git-send-email-daniel.thompson@linaro.org \
--to=daniel.thompson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).