From: John Garry <john.garry@huawei.com>
To: Will Deacon <will@kernel.org>,
Shaokun Zhang <zhangshaokun@hisilicon.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
Hanjun Guo <guohanjun@huawei.com>
Subject: Re: [PATCH] drivers/perf: hisi: update the sccl_id/ccl_id for certain HiSilicon platform
Date: Thu, 7 Nov 2019 11:50:30 +0000 [thread overview]
Message-ID: <52f89b8c-0baf-77d0-4bbd-1e129f8e5ed2@huawei.com> (raw)
In-Reply-To: <20191107114041.GB11587@willie-the-truck>
On 07/11/2019 11:40, Will Deacon wrote:
> Hi,
>
> On Thu, Nov 07, 2019 at 03:56:04PM +0800, Shaokun Zhang wrote:
>> @@ -338,8 +339,10 @@ void hisi_uncore_pmu_disable(struct pmu *pmu)
>>
>> /*
>> * Read Super CPU cluster and CPU cluster ID from MPIDR_EL1.
>> - * If multi-threading is supported, CCL_ID is the low 3-bits in MPIDR[Aff2]
>> - * and SCCL_ID is the upper 5-bits of Aff2 field; if not, SCCL_ID
>> + * If multi-threading is supported, On Huawei Kunpeng 920 SoC whose cpu
>> + * core is tsv110, CCL_ID is the low 3-bits in MPIDR[Aff2] and SCCL_ID
>> + * is the upper 5-bits of Aff2 field; while for other cpu types, SCCL_ID
>> + * is in MPIDR[Aff3] and CCL_ID is in MPIDR[Aff2], if not, SCCL_ID
>> * is in MPIDR[Aff2] and CCL_ID is in MPIDR[Aff1].
>> */
>> static void hisi_read_sccl_and_ccl_id(int *sccl_id, int *ccl_id)
>> @@ -347,12 +350,19 @@ static void hisi_read_sccl_and_ccl_id(int *sccl_id, int *ccl_id)
>> u64 mpidr = read_cpuid_mpidr();
>>
>> if (mpidr & MPIDR_MT_BITMASK) {
>> - int aff2 = MPIDR_AFFINITY_LEVEL(mpidr, 2);
>> -
>> - if (sccl_id)
>> - *sccl_id = aff2 >> 3;
>> - if (ccl_id)
>> - *ccl_id = aff2 & 0x7;
>> + if (read_cpuid_part_number() == HISI_CPU_PART_TSV110) {
>> + int aff2 = MPIDR_AFFINITY_LEVEL(mpidr, 2);
>> +
>> + if (sccl_id)
>> + *sccl_id = aff2 >> 3;
>> + if (ccl_id)
>> + *ccl_id = aff2 & 0x7;
>> + } else {
>> + if (sccl_id)
>> + *sccl_id = MPIDR_AFFINITY_LEVEL(mpidr, 3);
>> + if (ccl_id)
>> + *ccl_id = MPIDR_AFFINITY_LEVEL(mpidr, 2);
>> + }
>
> [I prefer Mark's version, so please reply to indicate whether or not it
> works for you]
Replying on Shaokun's behalf as he appears offline now.
In response to "> If TSV110 is always MT, ":
It isn't. There are 2 spins of Huawei Kunpeng 920 SoC which includes
TaishanV110 aka TSV110: one has the MT bit set and the other without.
We did ask for this not to be changed...
>
> So I'll take this, but the lesson here seems to be that it's a terrible idea
> to infer system topology from CPU ID registers. In future, I'm going to
> insist that this comes from firmware tables because hacks like the above are
> not sustainable.
>
Hopefully it will not change again, but maybe we can use PPTT instead.
Thanks,
John
> Will
> .
>
_______________________________________________
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:[~2019-11-07 11:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 7:56 [PATCH] drivers/perf: hisi: update the sccl_id/ccl_id for certain HiSilicon platform Shaokun Zhang
2019-11-07 11:31 ` Mark Rutland
2019-11-07 11:40 ` Will Deacon
2019-11-07 11:50 ` John Garry [this message]
2019-11-07 11:56 ` Mark Rutland
2019-11-07 12:06 ` John Garry
2019-11-07 12:11 ` Mark Rutland
2019-11-07 13:04 ` John Garry
2019-11-07 13:09 ` Will Deacon
2019-11-08 1:25 ` Shaokun Zhang
2019-11-08 9:49 ` Will Deacon
2019-11-09 2:51 ` [PATCH] drivers/perf: hisi: Simplify hisi_read_sccl_and_ccl_id and its comment Shaokun Zhang
2019-11-11 13:49 ` John Garry
2019-11-12 0:50 ` Shaokun Zhang
2019-11-08 1:18 ` [PATCH] drivers/perf: hisi: update the sccl_id/ccl_id for certain HiSilicon platform Shaokun Zhang
2019-11-08 1:15 ` Shaokun Zhang
2019-11-08 1:28 ` Shaokun Zhang
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=52f89b8c-0baf-77d0-4bbd-1e129f8e5ed2@huawei.com \
--to=john.garry@huawei.com \
--cc=guohanjun@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
--cc=zhangshaokun@hisilicon.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 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).