From: sashiko-bot@kernel.org
To: "Dhruv Gupta" <dhruv.gupta@amd.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [RFC PATCH] perf/x86/rapl: Fix a bug caused by overflow timer being calculated using a 200W Max TDP
Date: Wed, 11 Nov 2026 16:22:31 +0000 [thread overview]
Message-ID: <sashiko-outbox-209276@kernel.org> (raw)
In-Reply-To: <20261111151050.329724-1-dhruv.gupta@amd.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] perf/x86/rapl: 64-bit division in rapl_check_hw_unit() breaks
32-bit builds
--
commit 64815f3ce3036f1ab83ef82a1cc4dd1237aac3f9
Author: Dhruv Gupta <dhruv.gupta@amd.com>
perf/x86/rapl: Fix a bug caused by overflow timer being calculated using a 200W Max TDP
This commit raises the reference power used to compute the RAPL energy counter
overflow timer interval from 200W to 1000W and simplifies the interval
calculation in rapl_check_hw_unit().
> diff --git a/arch/x86/events/rapl.c b/arch/x86/events/rapl.c
> index 8ed03c32f5605..43ac9e1c98b45 100644
> --- a/arch/x86/events/rapl.c
> +++ b/arch/x86/events/rapl.c
> @@ -106,6 +106,7 @@ static const char *const rapl_core_domain_name __initconst = "core";
> */
> #define RAPL_EVENT_MASK 0xFFULL
> #define RAPL_CNTR_WIDTH 32
> +#define RAPL_TIMER_REF_WATTS 1000
>
> #define RAPL_EVENT_ATTR_STR(_name, v, str) \
> static struct perf_pmu_events_attr event_attr_##v = { \
> @@ -639,16 +640,12 @@ static int rapl_check_hw_unit(void)
>
> /*
> * Calculate the timer rate:
> - * Use reference of 200W for scaling the timeout to avoid counter
> - * overflows. 200W = 200 Joules/sec
> - * Divide interval by 2 to avoid lockstep (2 * 100)
> - * if hw unit is 32, then we use 2 ms 1/200/2
> + * Use reference of 1000W for scaling the timeout to avoid counter
> + * overflows. 1000W = 1000 Joules/sec
> + * Divide interval by 2 to avoid lockstep (2 * RAPL_TIMER_REF_WATTS)
> */
> - rapl_timer_ms = 2;
> - if (rapl_pkg_hw_unit[0] < 32) {
> - rapl_timer_ms = (1000 / (2 * 100));
> - rapl_timer_ms *= (1ULL << (32 - rapl_pkg_hw_unit[0] - 1));
> - }
> + rapl_timer_ms = (1000ULL << (32 - rapl_core_hw_unit)) /
> + (2 * RAPL_TIMER_REF_WATTS);
[Severity: High]
Does this 64-bit division break 32-bit x86 builds? Dividing the runtime
64-bit value (1000ULL << (32 - rapl_core_hw_unit)) by 2000 with the plain
/ operator emits a call to __udivdi3 on CONFIG_X86_32, causing a link
failure when CONFIG_PERF_EVENTS_INTEL_RAPL is enabled. Using div_u64()
would avoid this.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111151050.329724-1-dhruv.gupta@amd.com?part=1
next prev parent reply other threads:[~2026-11-11 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 15:10 [RFC PATCH] perf/x86/rapl: Fix a bug caused by overflow timer being calculated using a 200W Max TDP Dhruv Gupta
2026-11-11 16:22 ` sashiko-bot [this message]
2026-11-11 23:50 ` Borislav Petkov
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=sashiko-outbox-209276@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dhruv.gupta@amd.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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