From: daniel.thompson@linaro.org (Daniel Thompson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: Make IPI_CPU_BACKTRACE a "non-secure" SGI
Date: Fri, 18 Dec 2015 11:20:41 +0000 [thread overview]
Message-ID: <5673EC09.8090909@linaro.org> (raw)
In-Reply-To: <1450430173-26992-3-git-send-email-marc.zyngier@arm.com>
On 18/12/15 09:16, Marc Zyngier wrote:
> Having IPI_CPU_BACKTRACE as SGI15 may not work if the kernel is
> running in non-secure mode and that the secure firmware has
> decided to follow ARM's recommendations that SGI8-15 should
> be reserved for secure purpose.
>
> Now that we are "only" using SGI0-6, change IPI_CPU_BACKTRACE
> to use SGI7, which makes it more likely to work.
>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Tested-by: Daniel Thompson <daniel.thompson@linaro.org>
> ---
> arch/arm/kernel/smp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/kernel/smp.c b/arch/arm/kernel/smp.c
> index d50a77d..fe517f1 100644
> --- a/arch/arm/kernel/smp.c
> +++ b/arch/arm/kernel/smp.c
> @@ -72,7 +72,7 @@ enum ipi_msg_type {
> IPI_CPU_STOP,
> IPI_IRQ_WORK,
> IPI_COMPLETION,
> - IPI_CPU_BACKTRACE = 15,
> + IPI_CPU_BACKTRACE,
> };
>
> static DECLARE_COMPLETION(cpu_running);
>
next prev parent reply other threads:[~2015-12-18 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 9:16 [PATCH 0/2] IPI numbering cleanup Marc Zyngier
2015-12-18 9:16 ` [PATCH 1/2] ARM: Remove IPI_CALL_FUNC_SINGLE Marc Zyngier
2015-12-18 9:16 ` [PATCH 2/2] ARM: Make IPI_CPU_BACKTRACE a "non-secure" SGI Marc Zyngier
2015-12-18 9:34 ` Russell King - ARM Linux
2015-12-18 9:48 ` Marc Zyngier
2015-12-18 9:52 ` Russell King - ARM Linux
2015-12-18 11:20 ` Daniel Thompson [this message]
2015-12-18 11:29 ` Marc Zyngier
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=5673EC09.8090909@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).