From: Yicong Yang <yangyicong@huawei.com>
To: <will@kernel.org>, <mark.rutland@arm.com>,
<linux-arm-kernel@lists.infradead.org>
Cc: <james.clark@linaro.org>, <robh@kernel.org>,
<anshuman.khandual@arm.com>, <jonathan.cameron@huawei.com>,
<hejunhao3@huawei.com>, <linuxarm@huawei.com>,
<prime.zeng@hisilicon.com>, <xuwei5@huawei.com>,
<wangyushan12@huawei.com>, <yangyicong@hisilicon.com>
Subject: [PATCH 0/2] perf: arm_pmuv3: Don't use PMCCNTR_EL0 on SMT cores
Date: Tue, 12 Aug 2025 16:08:28 +0800 [thread overview]
Message-ID: <20250812080830.20796-1-yangyicong@huawei.com> (raw)
From: Yicong Yang <yangyicong@hisilicon.com>
This patchset fixed CPU_CYCLES counting on SMT system. CPU_CYCLES can use
PMCCNTR_EL0 which will count the hardware processor clock rather than the
PE clock (ARM DDI0487 L.b D13.1.3) on SMT cores which fails the users
expectation as CPU_CYCLES (0x0011) is defined to count on each PE cycles.
Fix this by avoid using PMCCNTR_EL0 on SMT cores when counting CPU_CYCLES.
Yicong Yang (2):
perf: arm_pmuv3: Factor out PMCCNTR_EL0 use conditions
perf: arm_pmuv3: Don't use PMCCNTR_EL0 on SMT cores
drivers/perf/arm_pmuv3.c | 39 +++++++++++++++++++++++++++++++++++++--
1 file changed, 37 insertions(+), 2 deletions(-)
--
2.24.0
next reply other threads:[~2025-08-12 12:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 8:08 Yicong Yang [this message]
2025-08-12 8:08 ` [PATCH 1/2] perf: arm_pmuv3: Factor out PMCCNTR_EL0 use conditions Yicong Yang
2025-08-12 10:02 ` James Clark
2025-08-12 10:25 ` Mark Rutland
2025-08-12 8:08 ` [PATCH 2/2] perf: arm_pmuv3: Don't use PMCCNTR_EL0 on SMT cores Yicong Yang
2025-08-12 10:00 ` James Clark
2025-08-12 10:14 ` Yicong Yang
2025-08-12 10:22 ` Mark Rutland
2025-08-13 8:17 ` Yicong Yang
2025-08-12 10:31 ` James Clark
2025-08-13 8:32 ` Yicong Yang
2025-08-12 10:33 ` Mark Rutland
2025-08-13 8:03 ` Yicong Yang
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=20250812080830.20796-1-yangyicong@huawei.com \
--to=yangyicong@huawei.com \
--cc=anshuman.khandual@arm.com \
--cc=hejunhao3@huawei.com \
--cc=james.clark@linaro.org \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=prime.zeng@hisilicon.com \
--cc=robh@kernel.org \
--cc=wangyushan12@huawei.com \
--cc=will@kernel.org \
--cc=xuwei5@huawei.com \
--cc=yangyicong@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).