From: linux@arm.linux.org.uk (Russell King - ARM Linux)
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 09:52:36 +0000 [thread overview]
Message-ID: <20151218095236.GO8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <5673D683.8050002@arm.com>
On Fri, Dec 18, 2015 at 09:48:51AM +0000, Marc Zyngier wrote:
> On 18/12/15 09:34, Russell King - ARM Linux wrote:
> > On Fri, Dec 18, 2015 at 09:16:13AM +0000, 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.
> >
> > We should add a comment to the enum explaining this, so it's obvious
> > for the future - best place is after the IPI_CPU_BACKTRACE entry.
> > Not everyone checks the git logs for these kinds of details.
>
> Indeed. How about something like this:
Yep.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-12-18 9:52 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 [this message]
2015-12-18 11:20 ` Daniel Thompson
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=20151218095236.GO8644@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.