From: Mark Rutland <mark.rutland@arm.com>
To: James Clark <james.clark@arm.com>,
will@kernel.org, catalin.marinas@arm.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-next@vger.kernel.org,
u.kleine-koenig@pengutronix.de,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v2 1/1] arm: perf: Fix ARCH=arm build with GCC
Date: Sat, 16 Dec 2023 12:44:33 +0000 [thread overview]
Message-ID: <ZX2bsYEdWVxTCiTi@FVFF77S0Q05N> (raw)
In-Reply-To: <20231215175648.3397170-2-james.clark@arm.com>
On Fri, Dec 15, 2023 at 05:56:48PM +0000, James Clark wrote:
> LLVM ignores everything inside the if statement and doesn't generate
> errors, but GCC doesn't ignore it, resulting in the following error:
>
> drivers/perf/arm_pmuv3.c: In function 'armv8pmu_write_evtype':
> include/linux/bits.h:34:29: error: left shift count >= width of type [-Werror=shift-count-overflow]
> 34 | (((~UL(0)) - (UL(1) << (l)) + 1) & \
>
> Fix it by using GENMASK_ULL which doesn't overflow on arm32 (even though
> the value is never used there).
It would be nice if this could explain the overflow problem, i.e.
| The GENMASK() macro creates masks of type unsigned long, and we use this to
| geenrate the ARMV8_PMU_EVTYPE_TH and ARMV8_PMU_EVTYPE_TC constants. These
| include bits above bit 31, and generating these requires shifting more than the
| size of unsigned long on 32-bit ARM.
|
| Consequently when building for 32-bit arm, GCC warns about their use:
|
| drivers/perf/arm_pmuv3.c: In function 'armv8pmu_write_evtype':
| include/linux/bits.h:34:29: error: left shift count >= width of type [-Werror=shift-count-overflow]
| 34 | (((~UL(0)) - (UL(1) << (l)) + 1) & \
|
| ... though LLVM does not warn as the actual usage is not reachable on 32-bit
| ARM due to `if (IS_ENABLED(...)` checks.
|
| Avoid the warning by using GENMACK_ULL(), which doesn't overflow on 32-bit arm.
> Fixes: 3115ee021bfb ("arm64: perf: Include threshold control fields in PMEVTYPER mask")
> Reported-by: Uwe Kleine-K"onig <u.kleine-koenig@pengutronix.de>
> Closes: https://lore.kernel.org/linux-arm-kernel/20231215120817.h2f3akgv72zhrtqo@pengutronix.de/
> Signed-off-by: James Clark <james.clark@arm.com>
Thanks for this!
Acked-by: Mark Rutland <mark.rutland@arm.com>
Will, Catalin, the broken commit is queued in the arm64 for-next/perf branch
(and merged into for-next/core); is this something we can easily fold in?
Mark.
> ---
> include/linux/perf/arm_pmuv3.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/perf/arm_pmuv3.h b/include/linux/perf/arm_pmuv3.h
> index 0f4d62ef3a9a..46377e134d67 100644
> --- a/include/linux/perf/arm_pmuv3.h
> +++ b/include/linux/perf/arm_pmuv3.h
> @@ -234,8 +234,8 @@
> * PMXEVTYPER: Event selection reg
> */
> #define ARMV8_PMU_EVTYPE_EVENT GENMASK(15, 0) /* Mask for EVENT bits */
> -#define ARMV8_PMU_EVTYPE_TH GENMASK(43, 32)
> -#define ARMV8_PMU_EVTYPE_TC GENMASK(63, 61)
> +#define ARMV8_PMU_EVTYPE_TH GENMASK_ULL(43, 32) /* arm64 only */
> +#define ARMV8_PMU_EVTYPE_TC GENMASK_ULL(63, 61) /* arm64 only */
>
> /*
> * Event filters for PMUv3
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-12-16 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 17:56 [PATCH v2 0/1] arm: perf: Fix ARCH=arm build with GCC James Clark
2023-12-15 17:56 ` [PATCH v2 1/1] " James Clark
2023-12-15 18:20 ` Uwe Kleine-König
2023-12-16 12:44 ` Mark Rutland [this message]
2023-12-17 13:41 ` [PATCH v2 0/1] " Will Deacon
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=ZX2bsYEdWVxTCiTi@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.clark@arm.com \
--cc=justinstitt@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=suzuki.poulose@arm.com \
--cc=u.kleine-koenig@pengutronix.de \
--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