From: Peter Zijlstra <peterz@infradead.org>
To: Aldo Conte <aldocontelk@gmail.com>
Cc: mingo@redhat.com, acme@kernel.org, namhyung@kernel.org,
tglx@kernel.org, bp@alien8.de, dave.hansen@linux.intel.com,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
james.clark@linaro.org, hpa@zytor.com, x86@kernel.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org
Subject: Re: [PATCH v2] perf/x86/intel/p4: Fix unused variable warning in p4_pmu_init()
Date: Tue, 24 Mar 2026 15:10:59 +0100 [thread overview]
Message-ID: <20260324141059.GG3738010@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260320112302.281549-1-aldocontelk@gmail.com>
On Fri, Mar 20, 2026 at 12:23:02PM +0100, Aldo Conte wrote:
> Build the kernel with make W=1 generates the following warning:
>
> arch/x86/events/intel/p4.c: In function ‘p4_pmu_init’:
> arch/x86/events/intel/p4.c:1370:27: error: variable ‘high’ set but not used [-Werror=unused-but-set-variable]
> 1370 | unsigned int low, high;
> | ^~~~
>
> This happens because, although both variables are declared and
> initialized by rdmsr, only `low` is used in the subsequent if statement.
>
> This patch uses the rdmsrq() macro instead of the rdmsr() macro.
> The rdmsrq() macro avoids the use of high and low variables
> because it reads the msr value in a single u64 variable.
> Also, replace (1 << 7) with the proper macro.
>
> Running `make W=1` again resolves the error.
> I was unable to test the patch because
> i do not have the hardware.
>
> Suggested-by: Dave Hansen <dave.hansen@linux.intel.com>
> Signed-off-by: Aldo Conte <aldocontelk@gmail.com>
> ---
> v2:
> - Use of rdmsrq() instead of rdmsr() to read the full 64-bit MSR
> in one single read avoiding the use of high and low.
> - Replace (1 << 7) with the MSR_IA32_MISC_ENABLE_EMON
> - Remove pr_cont() with MSR printout added in the previous patch
>
> v1: https://lore.kernel.org/all/20260319152210.210854-1-aldocontelk@gmail.com/
> arch/x86/events/intel/p4.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
In general I figure people using W=1 can keep the pieces, but the split
msr interface is a relic, so yeah, lets clean this up.
Thanks!
next prev parent reply other threads:[~2026-03-24 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 15:22 [PATCH] perf/x86/intel/p4: Fix unused variable warning in p4_pmu_init() Aldo Conte
2026-03-19 15:30 ` Dave Hansen
2026-03-19 22:20 ` Aldo Conte
2026-03-19 22:24 ` Dave Hansen
2026-03-20 11:23 ` [PATCH v2] " Aldo Conte
2026-03-24 14:10 ` Peter Zijlstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-20 11:13 Aldo Conte
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=20260324141059.GG3738010@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=aldocontelk@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
--cc=x86@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