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: [PATCH] ARM: smp: allow get the core count from L2 control on A15
Date: Tue, 31 Jan 2012 14:32:47 +0000	[thread overview]
Message-ID: <20120131143247.GB31004@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <4F27F8E8.1030703@samsung.com>

On Tue, Jan 31, 2012 at 02:21:28PM +0000, Kukjin Kim wrote:
> On 01/31/12 23:13, Will Deacon wrote:
> >
> > This doesn't belong in smp.c but, more importantly, this doesn't work for
> > multi-cluster configurations at all. Since all A15 implementations will be
> > on new platforms, the code will be device-tree only and so we should use
> 
> Why not? As I know, current arm kernel ARMv7 arch can support A15 
> without device-tree. And you know, the core number should be counted by 
> L2 control register. no?

I'll answer these in order:

1.) The code doesn't belong in smp.c because it's specific to the A15
2.) The architecture code may well support A15, but since there are no
    platforms in mainline that support A15 yet, then all new platforms will
    need to be DT-based. That means we can rely on the DT to provide this
    information.
3.) The L2 control register only tells you how many cores are hanging off
    that particular L2. This will be wrong for multi-cluster systems since
    it will only identify a subset of the cores.

> > I believe Lorenzo posted some patches which you could look at.
> >
> OK, Would be better.

Yes, I think it's the only way to solve this problem without adding an
architected method for enumerating the CPU topology.

Will

  reply	other threads:[~2012-01-31 14:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 12:11 [PATCH] ARM: smp: allow get the core count from L2 control on A15 Kukjin Kim
2012-01-31 14:13 ` Will Deacon
2012-01-31 14:21   ` Kukjin Kim
2012-01-31 14:32     ` Will Deacon [this message]
2012-01-31 14:40       ` Kukjin Kim
2012-01-31 15:20         ` Lorenzo Pieralisi
2012-01-31 18:03 ` Russell King - ARM Linux

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=20120131143247.GB31004@mudshark.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).