linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/8] Introduce logical CPU mapping
Date: Wed, 10 Aug 2011 09:58:24 +0100	[thread overview]
Message-ID: <20110810085824.GD10121@e102144-lin.cambridge.arm.com> (raw)
In-Reply-To: <4E424640.6040801@ti.com>

On Wed, Aug 10, 2011 at 09:50:08AM +0100, Santosh wrote:
> Will,

Hi Santosh,

> On Wednesday 10 August 2011 03:12 AM, Will Deacon wrote:
> > Hello,
> >
> > This patch series is an RFC following a discussion I had with Russell
> > the other day:
> >
> >   http://lists.infradead.org/pipermail/linux-arm-kernel/2011-August/060370.html
> >
> > The approach I've taken is fairly simple but is enough for booting on a
> > CPU with physical ID != 0 on platforms which can handle it.
> >
> > Note that I haven't touched the OMAP4 or Tegra platforms since it's not
> > clear from the code how they would be adapted to make use of the
> > physical CPU number.
> >
> On OMAP, we use hardware register hand-shake for boot between a boot CPU
> and non-boot CPU. On OMAP4, boot CPU has to be always CPU0 to ensure
> that security and firewall initialisation is taken care. Other CPU can't
> do those things.

Understood. We can leave OMAP like it is then and assume that bootloaders
will always ensure physical CPU0 is used for booting.

Cheers,

Will

      reply	other threads:[~2011-08-10  8:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09 21:42 [RFC PATCH 0/8] Introduce logical CPU mapping Will Deacon
2011-08-09 21:42 ` [RFC PATCH 1/8] ARM: cpuid: add support for reading MPIDR Will Deacon
2011-08-09 21:42 ` [RFC PATCH 2/8] ARM: smp: populate logical CPU mapping during boot Will Deacon
2011-08-09 21:42 ` [RFC PATCH 3/8] ARM: gic: convert logical CPU numbers into physical numbers Will Deacon
2011-08-11 15:04   ` Will Deacon
2011-08-09 21:42 ` [RFC PATCH 4/8] ARM: exynos4: convert logical CPU numbers to " Will Deacon
2011-08-10  1:07   ` Kyungmin Park
2011-08-10  8:46     ` Will Deacon
2011-08-10  8:49       ` Kyungmin Park
2011-08-10  8:57         ` Will Deacon
2011-08-09 21:42 ` [RFC PATCH 5/8] ARM: msm: " Will Deacon
2011-08-09 22:26   ` David Brown
2011-08-10  8:42     ` Will Deacon
2011-08-10 15:51       ` David Brown
2011-08-09 21:42 ` [RFC PATCH 6/8] ARM: shmobile: " Will Deacon
2011-08-09 21:42 ` [RFC PATCH 7/8] ARM: ux500: " Will Deacon
2011-08-11 13:31   ` Linus Walleij
2011-08-09 21:42 ` [RFC PATCH 8/8] ARM: versatile: " Will Deacon
2011-08-10  8:50 ` [RFC PATCH 0/8] Introduce logical CPU mapping Santosh
2011-08-10  8:58   ` Will Deacon [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=20110810085824.GD10121@e102144-lin.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --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).