public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARMv8 spin-table patches
Date: Wed, 16 Jul 2014 16:37:14 +0100	[thread overview]
Message-ID: <20140716153714.GA30313@leverpostej> (raw)
In-Reply-To: <53C43BC6.2020507@freescale.com>

On Mon, Jul 14, 2014 at 09:21:26PM +0100, York Sun wrote:
> On 07/14/2014 07:03 AM, Mark Rutland wrote:
> > Unfortunately I don't have an answer to that; the arm64 Linux spin-table
> > documentation and code were all written before I was involved.
> > 
> > The unfortunate truth is that a lot of the ARM DT and boot unification
> > work was done somewhat blindly, with many subtleties being lost. Someone
> > implemented spin-table with a shared address because it happened to be
> > easier, and then it got copied. Now that people are actively using it
> > it's not possible to remove it, and it's difficult to dissuade others
> > from following the crowd.
> > 
> > If U-Boot provides each CPU with its own unique address, then that would
> > be fantastic, and certainly avoids one nasty edge-case.
> 
> In the patch set I sent for review, each CPU has its own spin table. It has an
> option to use a single release address, or individual release address.

Ok, each having their own table is good.

I would strongly recommend against sharing the release address for the
reasons I described in my earlier email.

Cheers,
Mark.

      reply	other threads:[~2014-07-16 15:37 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
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 [this message]

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=20140716153714.GA30313@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