From: "Chen, Zide" <zide.chen@intel.com>
To: Dapeng Mi <dapeng1.mi@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
Eranian Stephane <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Dapeng Mi <dapeng1.mi@intel.com>,
Falcon Thomas <thomas.falcon@intel.com>,
Xudong Hao <xudong.hao@intel.com>
Subject: Re: [Patch v2 2/2] perf/x86: Update cap_user_rdpmc base on rdpmc user disable state
Date: Thu, 30 Apr 2026 09:22:33 -0700 [thread overview]
Message-ID: <d4728975-9194-4f8c-a858-a7f0e1fc1df6@intel.com> (raw)
In-Reply-To: <20260316050838.3624051-2-dapeng1.mi@linux.intel.com>
On 3/15/2026 10:08 PM, 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.
>
> 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>
>
> v2: Add is_x86_pmu() check before checking if rdpmc user disable feature
> is supported.
>
> v1: https://lore.kernel.org/all/20260311075201.2951073-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 66b1a873c395..34eda8813716 100644
> --- a/arch/x86/events/core.c
> +++ b/arch/x86/events/core.c
> @@ -2794,6 +2794,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 025f67726ecc..307361b106d2 100644
> --- a/arch/x86/events/perf_event.h
> +++ b/arch/x86/events/perf_event.h
> @@ -1351,8 +1351,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-04-30 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 5:08 [Patch v2 1/2] perf/x86: Introduce is_x86_pmu() helper Dapeng Mi
2026-03-16 5:08 ` [Patch v2 2/2] perf/x86: Update cap_user_rdpmc base on rdpmc user disable state Dapeng Mi
2026-04-30 16:22 ` Chen, Zide [this message]
2026-04-30 16:22 ` [Patch v2 1/2] perf/x86: Introduce is_x86_pmu() helper Chen, Zide
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=d4728975-9194-4f8c-a858-a7f0e1fc1df6@intel.com \
--to=zide.chen@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=thomas.falcon@intel.com \
--cc=xudong.hao@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