linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: vexpress: add support for multiple core tiles
Date: Mon, 6 Dec 2010 17:16:57 +0000	[thread overview]
Message-ID: <20101206171657.GH31777@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <006f01cb9563$faf32210$f0d96630$@deacon@arm.com>

On Mon, Dec 06, 2010 at 04:38:15PM -0000, Will Deacon wrote:
> Hi Russell,
> 
> > The other complication here is that the possible/present bitmaps use
> > logical CPU numbers, which depending on the platform may or may not
> > be the same as physical CPU numbers, even though it may be an A9 based
> > platform.
> 
> Eek. What sort of mapping do you get between logical and physical CPU
> numbers for these platforms? Are the logical numbers offset from the
> physical ones or is there just a random mapping between the two?

We currently have a 1:1 mapping between the two, but only because that's
a choice made entirely by the platform code.  The common code makes no
assumptions about the cpu number space it is using.

There are two places where logical and physical CPU numbers interact
come together:

1. boot_secondary / early startup code (via pen_release)
2. IPI sending in the GIC code

and this is where any platform can decide to place a mapping for whatever
reason.

      reply	other threads:[~2010-12-06 17:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29 17:48 [PATCH v3] ARM: vexpress: add support for multiple core tiles Will Deacon
2010-12-06 15:53 ` Russell King - ARM Linux
2010-12-06 16:38   ` Will Deacon
2010-12-06 17:16     ` Russell King - ARM Linux [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=20101206171657.GH31777@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 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).