From: Anshuman Khandual <anshuman.khandual@arm.com>
To: James Clark <james.clark@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, suzuki.poulose@arm.com,
will@kernel.org, mark.rutland@arm.com
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/3] arm64: perf: Include threshold control fields in PMEVTYPER mask
Date: Wed, 22 Nov 2023 14:14:52 +0530 [thread overview]
Message-ID: <347fc210-8c31-47be-a87a-656fa30a72ef@arm.com> (raw)
In-Reply-To: <20231113112507.917107-2-james.clark@arm.com>
On 11/13/23 16:55, James Clark wrote:
> FEAT_PMUv3_TH (Armv8.8) adds two new fields to PMEVTYPER, so include
> them in the mask. These aren't writable on 32 bit kernels as they are in
> the high part of the register, so only include them for arm64.
>
> It would be difficult to do this statically in the asm header files for
> each platform without resulting in circular includes or #ifdefs inline
> in the code. For that reason the ARMV8_PMU_EVTYPE_MASK definition has
> been removed and the mask is constructed programmatically.
Agreed, and this also makes sense because there is just a single instance
for ARMV8_PMU_EVTYPE_MASK in armv8pmu_write_evtype().
>
> Signed-off-by: James Clark <james.clark@arm.com>
> ---
> drivers/perf/arm_pmuv3.c | 9 ++++++++-
> include/linux/perf/arm_pmuv3.h | 3 ++-
> 2 files changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/perf/arm_pmuv3.c b/drivers/perf/arm_pmuv3.c
> index 6ca7be05229c..1d40d794f5e4 100644
> --- a/drivers/perf/arm_pmuv3.c
> +++ b/drivers/perf/arm_pmuv3.c
> @@ -555,8 +555,15 @@ static void armv8pmu_write_counter(struct perf_event *event, u64 value)
> static inline void armv8pmu_write_evtype(int idx, u32 val)
> {
> u32 counter = ARMV8_IDX_TO_COUNTER(idx);
> + unsigned long mask = ARMV8_PMU_EVTYPE_EVENT |
> + ARMV8_PMU_INCLUDE_EL2 |
> + ARMV8_PMU_EXCLUDE_EL0 |
> + ARMV8_PMU_EXCLUDE_EL1;
At first this looks bit odd sequence - EL2, EL0, EL1 but such as these
bit positions.
#define ARMV8_PMU_EXCLUDE_EL1 (1U << 31)
#define ARMV8_PMU_EXCLUDE_EL0 (1U << 30)
#define ARMV8_PMU_INCLUDE_EL2 (1U << 27)
>
> - val &= ARMV8_PMU_EVTYPE_MASK;
> + if (IS_ENABLED(CONFIG_ARM64))
> + mask |= ARMV8_PMU_EVTYPE_TC | ARMV8_PMU_EVTYPE_TH;
This makes sense.
> +
> + val &= mask;
> write_pmevtypern(counter, val);
> }
>
> diff --git a/include/linux/perf/arm_pmuv3.h b/include/linux/perf/arm_pmuv3.h
> index 9c226adf938a..ddd1fec86739 100644
> --- a/include/linux/perf/arm_pmuv3.h
> +++ b/include/linux/perf/arm_pmuv3.h
> @@ -228,7 +228,8 @@
> /*
> * PMXEVTYPER: Event selection reg
> */
> -#define ARMV8_PMU_EVTYPE_MASK 0xc800ffff /* Mask for writable bits */
> +#define ARMV8_PMU_EVTYPE_TH GENMASK(43, 32)
> +#define ARMV8_PMU_EVTYPE_TC GENMASK(63, 61)
Looks correct.
> #define ARMV8_PMU_EVTYPE_EVENT 0xffff /* Mask for EVENT bits */
>
> /*
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
_______________________________________________
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:[~2023-11-22 8:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 11:25 [PATCH v5 0/3] arm64: perf: Add support for event counting threshold James Clark
2023-11-13 11:25 ` [PATCH v5 1/3] arm64: perf: Include threshold control fields in PMEVTYPER mask James Clark
2023-11-21 10:15 ` Suzuki K Poulose
2023-11-22 8:44 ` Anshuman Khandual [this message]
2023-11-13 11:25 ` [PATCH v5 2/3] arm64: perf: Add support for event counting threshold James Clark
2023-11-21 10:20 ` Suzuki K Poulose
2023-11-23 3:42 ` Anshuman Khandual
2023-11-23 17:53 ` James Clark
2023-11-13 11:25 ` [PATCH v5 3/3] Documentation: arm64: Document the PMU event counting threshold feature James Clark
2023-11-20 21:31 ` Namhyung Kim
2023-11-21 10:33 ` Suzuki K Poulose
2023-11-23 15:33 ` James Clark
2023-11-23 5:50 ` Anshuman Khandual
2023-11-23 15:45 ` James Clark
2023-11-24 9:52 ` James Clark
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=347fc210-8c31-47be-a87a-656fa30a72ef@arm.com \
--to=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=james.clark@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=suzuki.poulose@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;
as well as URLs for NNTP newsgroup(s).