From: Valentin Schneider <valentin.schneider@arm.com>
To: "Zengtao \(B\)" <prime.zeng@hisilicon.com>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
Jeremy Linton <Jeremy.Linton@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>
Subject: Re: [PATCH] arm64: topology: Stop using MPIDR for topology information
Date: Wed, 09 Sep 2020 12:21:03 +0100 [thread overview]
Message-ID: <jhjzh5z5h7k.mognet@arm.com> (raw)
In-Reply-To: <678F3D1BB717D949B966B68EAEB446ED482431A1@DGGEMM506-MBX.china.huawei.com>
On 03/09/20 02:44, B wrote:
>> -----Original Message-----
>> From: Valentin Schneider [mailto:valentin.schneider@arm.com]
>> On 02/09/20 04:24, B wrote:
>> > I agree with your idea to remove the topology functionality of MPIDR ,
>> > but I think we need also consider ARM32 and GIC.
>> >
>>
>> Could you please elaborate? This change doesn't impact arch_topology, so
>> only arm64 is affected.
>
> Yes, this change only affects arm64, my question is that do we need to
> leverage it to arm32 since arm32 got the same issue.
>
> And for GIC we are also using MPIDR for the topology info, but I am sure
> It's got the same issue or not, just a suggestion to have a look.
So technically yes, we can be bothered by this on arm32 - Sudeep pointed
out a list of DT files that shows platforms with non-zero values in Aff1 or
above.
However, the bigger issue is that artificial separation in clusters of 16
CPUs due to extra limitations on Aff0 (mainly due to GICv3 AIUI). Given
that GICv2 can support at most 8 CPU interfaces, I don't think we have it
as bad on arm32.
WARNING: multiple messages have this Message-ID (diff)
From: Valentin Schneider <valentin.schneider@arm.com>
To: "Zengtao \(B\)" <prime.zeng@hisilicon.com>
Cc: Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jeremy Linton <Jeremy.Linton@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: topology: Stop using MPIDR for topology information
Date: Wed, 09 Sep 2020 12:21:03 +0100 [thread overview]
Message-ID: <jhjzh5z5h7k.mognet@arm.com> (raw)
In-Reply-To: <678F3D1BB717D949B966B68EAEB446ED482431A1@DGGEMM506-MBX.china.huawei.com>
On 03/09/20 02:44, B wrote:
>> -----Original Message-----
>> From: Valentin Schneider [mailto:valentin.schneider@arm.com]
>> On 02/09/20 04:24, B wrote:
>> > I agree with your idea to remove the topology functionality of MPIDR ,
>> > but I think we need also consider ARM32 and GIC.
>> >
>>
>> Could you please elaborate? This change doesn't impact arch_topology, so
>> only arm64 is affected.
>
> Yes, this change only affects arm64, my question is that do we need to
> leverage it to arm32 since arm32 got the same issue.
>
> And for GIC we are also using MPIDR for the topology info, but I am sure
> It's got the same issue or not, just a suggestion to have a look.
So technically yes, we can be bothered by this on arm32 - Sudeep pointed
out a list of DT files that shows platforms with non-zero values in Aff1 or
above.
However, the bigger issue is that artificial separation in clusters of 16
CPUs due to extra limitations on Aff0 (mainly due to GICv3 AIUI). Given
that GICv2 can support at most 8 CPU interfaces, I don't think we have it
as bad on arm32.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-09 11:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 13:00 [PATCH] arm64: topology: Stop using MPIDR for topology information Valentin Schneider
2020-08-29 13:00 ` Valentin Schneider
2020-09-02 3:24 ` Zengtao (B)
2020-09-02 3:24 ` Zengtao (B)
2020-09-02 10:50 ` Sudeep Holla
2020-09-02 10:50 ` Sudeep Holla
2020-09-02 10:52 ` Valentin Schneider
2020-09-02 10:52 ` Valentin Schneider
2020-09-03 1:44 ` Zengtao (B)
2020-09-03 1:44 ` Zengtao (B)
2020-09-09 11:21 ` Valentin Schneider [this message]
2020-09-09 11:21 ` Valentin Schneider
2020-09-02 10:04 ` Sudeep Holla
2020-09-02 10:04 ` Sudeep Holla
2020-09-02 10:52 ` Valentin Schneider
2020-09-02 10:52 ` Valentin Schneider
2020-09-07 21:35 ` Will Deacon
2020-09-07 21:35 ` Will Deacon
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=jhjzh5z5h7k.mognet@arm.com \
--to=valentin.schneider@arm.com \
--cc=Jeremy.Linton@arm.com \
--cc=catalin.marinas@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=prime.zeng@hisilicon.com \
--cc=robin.murphy@arm.com \
--cc=sudeep.holla@arm.com \
--cc=will@kernel.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 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.