From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drivers/perf: hisi: update the sccl_id/ccl_id when MT is supported
Date: Tue, 24 Jul 2018 15:39:29 +0100 [thread overview]
Message-ID: <20180724143929.GA22465@arm.com> (raw)
In-Reply-To: <e4f0cfe5-0724-1551-01ea-ab26c8aee229@hisilicon.com>
On Tue, Jul 24, 2018 at 07:06:11PM +0800, Zhangshaokun wrote:
> On 2018/7/23 22:42, Will Deacon wrote:
> > On Thu, Jul 19, 2018 at 07:26:40PM +0800, Shaokun Zhang wrote:
> >> MT bit in MPIDR_EL1 is now supported in certain HiSilicon platforms, so
> >> the mapping between sccl_id/ccl_id and affinity level needs to be updated
> >> from the generic encoding we originally used.
> >>
> >> Cc: John Garry <john.garry@huawei.com>
> >> Cc: Will Deacon <will.deacon@arm.com>
> >> Cc: Mark Rutland <mark.rutland@arm.com>
> >> Signed-off-by: Shaokun Zhang <zhangshaokun@hisilicon.com>
> >> ---
> >> drivers/perf/hisilicon/hisi_uncore_pmu.c | 13 ++++++++-----
> >> 1 file changed, 8 insertions(+), 5 deletions(-)
> >>
> >> diff --git a/drivers/perf/hisilicon/hisi_uncore_pmu.c b/drivers/perf/hisilicon/hisi_uncore_pmu.c
> >> index 44df613..b3c5ae9 100644
> >> --- a/drivers/perf/hisilicon/hisi_uncore_pmu.c
> >> +++ b/drivers/perf/hisilicon/hisi_uncore_pmu.c
> >> @@ -350,19 +350,22 @@ void hisi_uncore_pmu_disable(struct pmu *pmu)
> >>
> >> /*
> >> * Read Super CPU cluster and CPU cluster ID from MPIDR_EL1.
> >> - * If multi-threading is supported, 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]. If this changes in future, this shall be updated.
> >> + * 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
> >> + * is in MPIDR[Aff2] and CCL_ID is in MPIDR[Aff1]. If this changes in
> >> + * future, this shall be updated.
> >> */
> >> static void hisi_read_sccl_and_ccl_id(int *sccl_id, int *ccl_id)
> >> {
> >> u64 mpidr = read_cpuid_mpidr();
> >>
> >> if (mpidr & MPIDR_MT_BITMASK) {
> >
> > So, to be clear, you're saying that the MT bit was not set in any previous
> > SoC with this PMU, and therefore changing this logic doesn't introduce a
> > functional regression?
> >
>
> Yes, you are right. When the driver was developed, the MT bit was not supported
> and I was told that it may be set later in certain HiSilicon platform, therefore
> I checked this field in the code.
> Now the MT bit is set in one platform, but the mapping between sccl_id/ccl_id and
> affinity level is different from the origin encoding and needs to be updated.
> Of course, there is no functional regression.
>
> > Assuming that's the case, and you now have an SoC with MT set, then I don't
> > think the comment above which says "If this changes in future, this shall be
> > updated" can be correct, because changing the mapping will regress an older
> > platform, won't it?
> >
>
> Agree, at the beginning, I am not sure about it in future. I will take this
> information to the SoC team and drop this comment in next version.
It's ok, I can drop the comment when I apply the patch.
Thanks,
Will
prev parent reply other threads:[~2018-07-24 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 11:26 [PATCH] drivers/perf: hisi: update the sccl_id/ccl_id when MT is supported Shaokun Zhang
2018-07-23 14:42 ` Will Deacon
2018-07-24 11:06 ` Zhangshaokun
2018-07-24 14:39 ` Will Deacon [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=20180724143929.GA22465@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).