From: Anshuman Khandual <anshuman.khandual@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH] drivers: perf: arm_pmuv3: Update 'pmc_width' based on actual HW event width
Date: Mon, 9 Oct 2023 10:07:24 +0530 [thread overview]
Message-ID: <20231009043724.175100-1-anshuman.khandual@arm.com> (raw)
This updates 'perf_event_mmap_page->pmc_width' based on actual HW event's
width that are currently missing i.e ARMPMU_EVT_63BIT and ARMPMU_EVT_47BIT.
Cc: Will Deacon <will@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
---
This applies on v6.6-rc5.
drivers/perf/arm_pmuv3.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/perf/arm_pmuv3.c b/drivers/perf/arm_pmuv3.c
index fe4db1831662..94723d00548e 100644
--- a/drivers/perf/arm_pmuv3.c
+++ b/drivers/perf/arm_pmuv3.c
@@ -1375,6 +1375,10 @@ void arch_perf_update_userpage(struct perf_event *event,
if (userpg->cap_user_rdpmc) {
if (event->hw.flags & ARMPMU_EVT_64BIT)
userpg->pmc_width = 64;
+ else if (event->hw.flags & ARMPMU_EVT_63BIT)
+ userpg->pmc_width = 63;
+ else if (event->hw.flags & ARMPMU_EVT_47BIT)
+ userpg->pmc_width = 47;
else
userpg->pmc_width = 32;
}
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-10-09 4:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 4:37 Anshuman Khandual [this message]
2023-10-09 9:43 ` [PATCH] drivers: perf: arm_pmuv3: Update 'pmc_width' based on actual HW event width James Clark
2023-10-10 3:03 ` Anshuman Khandual
2023-10-10 8:28 ` James Clark
2023-10-10 8:30 ` James Clark
2023-10-10 11:38 ` Robin Murphy
2023-10-12 9:05 ` Mark Rutland
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=20231009043724.175100-1-anshuman.khandual@arm.com \
--to=anshuman.khandual@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox