From: Mark Rutland <mark.rutland@arm.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARMv8 spin-table patches
Date: Fri, 4 Jul 2014 10:29:09 +0100 [thread overview]
Message-ID: <20140704092909.GE31812@leverpostej> (raw)
In-Reply-To: <20140627164405.GY9006@bill-the-cat>
Hi,
Apologies for the late reply.
On Fri, Jun 27, 2014 at 05:44:05PM +0100, Tom Rini wrote:
> On Fri, Jun 27, 2014 at 09:11:39AM -0700, York Sun wrote:
>
> > Dear Albert, Wolfgang, Tom,
> >
> > I have seen some patches for PSCI. We don't have PSCI enabled on
> > Freescale ARMv8 SoCs. Will spin-table patches be acceptable?
>
> Baring some technical reasons why no, you can't do that, yes, lets see
> the patches :)
I'd point out that it's decidedly sub-optimal as spin-table provides no
provision for CPU hotplug (which for Linux will affect kexec and other
features relying on CPU hotplug support).
Additionally, spin-table has the unfortunate property of allowing the
firmware to throw an unbound number of CPUs into the kernel at once
(when they share a cpu-release-addr), where they can spend a lot of time
spinning pointlessly (executing kernel code from memory and possibly
fetching it into I-caches) depending on the number of events a CPU
happens to generate at runtime.
Linux will continue to support spin-table, but it's far preferable to
use PSCI.
Another possibility raised was trying to fix spin-table to provide
provisions for CPU hotplug, but I've not had the time to look into this
in great detail.
A while ago there were some PSCI patches for (32-bit) ARM [1]...
Thanks,
Mark.
[1] https://git.kernel.org/cgit/linux/kernel/git/maz/u-boot.git/log/?h=wip/psci-v4
next prev parent reply other threads:[~2014-07-04 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 16:11 [U-Boot] ARMv8 spin-table patches York Sun
2014-06-27 16:44 ` Tom Rini
2014-07-04 9:29 ` Mark Rutland [this message]
2014-07-08 3:48 ` Scott Wood
2014-07-14 14:03 ` Mark Rutland
2014-07-14 20:21 ` York Sun
2014-07-16 15:37 ` Mark Rutland
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=20140704092909.GE31812@leverpostej \
--to=mark.rutland@arm.com \
--cc=u-boot@lists.denx.de \
/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