public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
Cc: 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>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	Dapeng Mi <dapeng1.mi@intel.com>, Zide Chen <zide.chen@intel.com>,
	Falcon Thomas <thomas.falcon@intel.com>,
	Xudong Hao <xudong.hao@intel.com>
Subject: Re: [Patch v2 7/7] perf/x86/intel: Add support for rdpmc user disable feature
Date: Tue, 13 Jan 2026 11:51:30 +0100	[thread overview]
Message-ID: <20260113105130.GW830755@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <35123882-b909-43b7-879d-f3802dca2da1@linux.intel.com>

On Tue, Jan 13, 2026 at 10:29:38AM +0800, Mi, Dapeng wrote:
> 
> On 1/12/2026 6:57 PM, Peter Zijlstra wrote:
> > On Mon, Jan 12, 2026 at 01:16:49PM +0800, Dapeng Mi wrote:
> >
> >> +static void intel_pmu_update_rdpmc_user_disable(struct perf_event *event)
> >> +{
> >> +	/*
> >> +	 * Counter scope's user-space rdpmc is disabled by default
> >> +	 * except two cases.
> >> +	 * a. rdpmc = 2 (user space rdpmc enabled unconditionally)
> >> +	 * b. rdpmc = 1 and the event is not a system-wide event.
> >> +	 *    The count of non-system-wide events would be cleared when
> >> +	 *    context switches, so no count data is leaked.
> >> +	 */
> >> +	if (x86_pmu_has_rdpmc_user_disable(event->pmu)) {
> >> +		if (x86_pmu.attr_rdpmc == X86_USER_RDPMC_ALWAYS_ENABLE ||
> >> +		    (x86_pmu.attr_rdpmc == X86_USER_RDPMC_CONDITIONAL_ENABLE &&
> >> +		     event->ctx->task))
> >> +			event->hw.config &= ~ARCH_PERFMON_EVENTSEL_RDPMC_USER_DISABLE;
> >> +		else
> >> +			event->hw.config |= ARCH_PERFMON_EVENTSEL_RDPMC_USER_DISABLE;
> >> +	}
> >> +}
> > Is it not simpler to invert that condition?
> >
> > 	if (x86_pmu.attr_rdpmc == X86_USER_RDPMC_ALWAYS_NEVER ||
> > 	    !event->ctx->task)
> > 		event->hw.config |= ARCH_PERFMON_EVENTSEL_RDPMC_USER_DISABLE;
> > 	else
> > 		event->hw.config &= ~ARCH_PERFMON_EVENTSEL_RDPMC_USER_DISABLE;
> 
> Hmm, it seems the logic changes along with the code change. The system-wide
> event should be allowed to read with rdpmc from user space when attr_rdpmc
> == X86_USER_RDPMC_ALWAYS_ENABLE, but it doesn't with the new code.

Bah, indeed. Oh well.

  reply	other threads:[~2026-01-13 10:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12  5:16 [Patch v2 0/7] Enable core PMU for DMR and NVL Dapeng Mi
2026-01-12  5:16 ` [Patch v2 1/7] perf/x86/intel: Support the 4 new OMR MSRs introduced in " Dapeng Mi
2026-01-12 10:27   ` Peter Zijlstra
2026-01-13  1:22     ` Mi, Dapeng
2026-01-12  5:16 ` [Patch v2 2/7] perf/x86/intel: Add support for PEBS memory auxiliary info field in DMR Dapeng Mi
2026-01-12  5:16 ` [Patch v2 3/7] perf/x86/intel: Add core PMU support for DMR Dapeng Mi
2026-01-12 10:41   ` Peter Zijlstra
2026-01-13  1:59     ` Mi, Dapeng
2026-01-12  5:16 ` [Patch v2 4/7] perf/x86/intel: Add support for PEBS memory auxiliary info field in NVL Dapeng Mi
2026-01-12  5:16 ` [Patch v2 5/7] perf/x86/intel: Add core PMU support for Novalake Dapeng Mi
2026-01-12  5:16 ` [Patch v2 6/7] perf/x86: Use macros to replace magic numbers in attr_rdpmc Dapeng Mi
2026-01-12  5:16 ` [Patch v2 7/7] perf/x86/intel: Add support for rdpmc user disable feature Dapeng Mi
2026-01-12 10:57   ` Peter Zijlstra
2026-01-13  2:29     ` Mi, Dapeng
2026-01-13 10:51       ` Peter Zijlstra [this message]
2026-01-13  1:49   ` Ian Rogers
2026-01-13  2:49     ` Mi, Dapeng
2026-03-10  0:04   ` Ian Rogers
2026-03-10  5:28     ` 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=20260113105130.GW830755@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --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=thomas.falcon@intel.com \
    --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