From: "Falcon, Thomas" <thomas.falcon@intel.com>
To: "alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"acme@kernel.org" <acme@kernel.org>,
"dapeng1.mi@linux.intel.com" <dapeng1.mi@linux.intel.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"Hunter, Adrian" <adrian.hunter@intel.com>,
"namhyung@kernel.org" <namhyung@kernel.org>,
"Rogers, Ian" <irogers@google.com>,
"Eranian, Stephane" <eranian@google.com>
Cc: "Chen, Zide" <zide.chen@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"Mi, Dapeng1" <dapeng1.mi@intel.com>,
"Hao, Xudong" <xudong.hao@intel.com>
Subject: Re: [PATCH 3/8] perf/x86: Update cap_user_rdpmc base on rdpmc user disable state
Date: Fri, 5 Jun 2026 17:15:46 +0000 [thread overview]
Message-ID: <fdcb1f3211a493a538fe840f432b36ea073cf92b.camel@intel.com> (raw)
In-Reply-To: <20260605011136.2043393-4-dapeng1.mi@linux.intel.com>
On Fri, 2026-06-05 at 09:11 +0800, Dapeng Mi wrote:
> After introducing the RDPMC user disable feature, user-space RDPMC
> may
> return 0 instead of the actual event count. This creates an
> inconsistency
> with cap_user_rdpmc, where cap_user_rdpmc is set, but user-space
> RDPMC
> only returns 0.
>
> To accurately represent the user-space RDPMC capability, update
> cap_user_rdpmc based on the RDPMC user disable state. If RDPMC user
> disable is enabled, cap_user_rdpmc is set to false, allowing user-
> space
> programs to fall back to the read() syscall to obtain the real event
> count.
>
> Since arch_perf_update_userpage() could be called for software
> events,
> enhance x86_pmu_has_rdpmc_user_disable() to only check the x86 PMUs.
LGTM.
Reviewed-by: Thomas Falcon <thomas.falcon@intel.com>
Thanks,
Tom
>
> Fixes: 59af95e028d4 ("perf/x86/intel: Add support for rdpmc user
> disable feature")
> Signed-off-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
> Reviewed-by: Zide Chen <zide.chen@intel.com>
> ---
>
> Original patch link:
> https://lore.kernel.org/all/20260316050838.3624051-2-dapeng1.mi@linux.intel.com/
>
> arch/x86/events/core.c | 3 +++
> arch/x86/events/perf_event.h | 5 +++--
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
> index 3bd0522afe6d..6cd95b8e31cb 100644
> --- a/arch/x86/events/core.c
> +++ b/arch/x86/events/core.c
> @@ -2797,6 +2797,9 @@ void arch_perf_update_userpage(struct
> perf_event *event,
> userpg->cap_user_time_zero = 0;
> userpg->cap_user_rdpmc =
> !!(event->hw.flags & PERF_EVENT_FLAG_USER_READ_CNT);
> + if (x86_pmu_has_rdpmc_user_disable(event->pmu) &&
> + event->hw.config &
> ARCH_PERFMON_EVENTSEL_RDPMC_USER_DISABLE)
> + userpg->cap_user_rdpmc = 0;
> userpg->pmc_width = x86_pmu.cntval_bits;
>
> if (!using_native_sched_clock() || !sched_clock_stable())
> diff --git a/arch/x86/events/perf_event.h
> b/arch/x86/events/perf_event.h
> index dbb5c8e8a8ea..4003e2e0aa9c 100644
> --- a/arch/x86/events/perf_event.h
> +++ b/arch/x86/events/perf_event.h
> @@ -1359,8 +1359,9 @@ static inline u64
> x86_pmu_get_event_config(struct perf_event *event)
>
> static inline bool x86_pmu_has_rdpmc_user_disable(struct pmu *pmu)
> {
> - return !!(hybrid(pmu, config_mask) &
> - ARCH_PERFMON_EVENTSEL_RDPMC_USER_DISABLE);
> + return is_x86_pmu(pmu) &&
> + (hybrid(pmu, config_mask) &
> + ARCH_PERFMON_EVENTSEL_RDPMC_USER_DISABLE);
> }
>
> extern struct event_constraint emptyconstraint;
next prev parent reply other threads:[~2026-06-05 17:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 1:11 [PATCH 0/8] perf/x86: Miscellaneous PMU bug fixes Dapeng Mi
2026-06-05 1:11 ` [PATCH 1/8] perf/x86/intel: Remove anythread_deprecated bit from perf_capabilities Dapeng Mi
2026-06-05 17:04 ` Falcon, Thomas
2026-06-08 1:37 ` Mi, Dapeng
2026-06-05 1:11 ` [PATCH 2/8] perf/x86: Introduce is_x86_pmu() helper Dapeng Mi
2026-06-05 17:08 ` Falcon, Thomas
2026-06-05 1:11 ` [PATCH 3/8] perf/x86: Update cap_user_rdpmc base on rdpmc user disable state Dapeng Mi
2026-06-05 17:15 ` Falcon, Thomas [this message]
2026-06-05 1:11 ` [PATCH 4/8] perf/x86/intel: Fix redundant branch type check in intel_pmu_lbr_filter() Dapeng Mi
2026-06-05 18:28 ` Falcon, Thomas
2026-06-08 1:56 ` Mi, Dapeng
2026-06-08 6:15 ` Mi, Dapeng
2026-06-05 1:11 ` [PATCH 5/8] perf/x86/intel: Fix kernel address leakages in LBR stack Dapeng Mi
2026-06-05 1:11 ` [PATCH 6/8] perf/x86/intel: Validate return value of intel_pmu_init_hybrid() Dapeng Mi
2026-06-05 16:17 ` Chen, Zide
2026-06-08 2:48 ` Mi, Dapeng
2026-06-05 18:47 ` Falcon, Thomas
2026-06-05 1:11 ` [PATCH 7/8] perf/x86/intel: Drop fixed-counter PEBS constraints for baseline PEBS Dapeng Mi
2026-06-05 20:32 ` Chen, Zide
2026-06-08 2:46 ` Mi, Dapeng
2026-06-08 15:46 ` Chen, Zide
2026-06-09 0:36 ` Mi, Dapeng
2026-06-05 1:11 ` [PATCH 8/8] perf/core: Fix kernel register info leak via hardware skid Dapeng Mi
2026-06-05 19:08 ` Falcon, Thomas
2026-06-08 2:47 ` Mi, Dapeng
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=fdcb1f3211a493a538fe840f432b36ea073cf92b.camel@intel.com \
--to=thomas.falcon@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dapeng1.mi@intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=xudong.hao@intel.com \
--cc=zide.chen@intel.com \
/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