All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>,
	"rmk+kernel@arm.linux.org.uk" <rmk+kernel@arm.linux.org.uk>
Subject: Re: [PATCH] ARM: smp: allow get the core count from L2 control on A15
Date: Tue, 31 Jan 2012 23:40:41 +0900	[thread overview]
Message-ID: <4F27FD69.7060207@samsung.com> (raw)
In-Reply-To: <20120131143247.GB31004@mudshark.cambridge.arm.com>

On 01/31/12 23:32, Will Deacon wrote:
> 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:

Hmm, let
>
> 1.) The code doesn't belong in smp.c because it's specific to the A15

Yes, agree. So I just commented in my patch, I'm not sure where it 
should be added at.

> 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.

Well, I will submit EXYNOS5 which has two A15 cores today and I don't 
know why it should be supported only with DT, EXYNOS5 DT supporting will 
be submitted though.

> 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.

OK, let me check it.

>
>>> 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.
>
I'm not sure it is the only way...

Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
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 23:40:41 +0900	[thread overview]
Message-ID: <4F27FD69.7060207@samsung.com> (raw)
In-Reply-To: <20120131143247.GB31004@mudshark.cambridge.arm.com>

On 01/31/12 23:32, Will Deacon wrote:
> 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:

Hmm, let
>
> 1.) The code doesn't belong in smp.c because it's specific to the A15

Yes, agree. So I just commented in my patch, I'm not sure where it 
should be added at.

> 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.

Well, I will submit EXYNOS5 which has two A15 cores today and I don't 
know why it should be supported only with DT, EXYNOS5 DT supporting will 
be submitted though.

> 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.

OK, let me check it.

>
>>> 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.
>
I'm not sure it is the only way...

Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

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

Thread overview: 14+ 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 12:11 ` Kukjin Kim
2012-01-31 14:13 ` Will Deacon
2012-01-31 14:13   ` Will Deacon
2012-01-31 14:21   ` Kukjin Kim
2012-01-31 14:21     ` Kukjin Kim
2012-01-31 14:32     ` Will Deacon
2012-01-31 14:32       ` Will Deacon
2012-01-31 14:40       ` Kukjin Kim [this message]
2012-01-31 14:40         ` Kukjin Kim
2012-01-31 15:20         ` Lorenzo Pieralisi
2012-01-31 15:20           ` Lorenzo Pieralisi
2012-01-31 18:03 ` Russell King - ARM Linux
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=4F27FD69.7060207@samsung.com \
    --to=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=will.deacon@arm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.