From: Peter Zijlstra <peterz@infradead.org>
To: John Hubbard <jhubbard@nvidia.com>
Cc: "Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Ingo Molnar" <mingo@redhat.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>, "Ian Rogers" <irogers@google.com>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"James Clark" <james.clark@linaro.org>,
intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-perf-users@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] complete perf_allow_* trio and use in drm/xe
Date: Sat, 23 May 2026 10:40:56 +0200 [thread overview]
Message-ID: <20260523084056.GE3102624@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260523013326.129491-1-jhubbard@nvidia.com>
On Fri, May 22, 2026 at 06:33:24PM -0700, John Hubbard wrote:
> perf_allow_cpu() and perf_allow_tracepoint() are static inline and
> reach into a non-exported sysctl, so modular drivers that want the
> same permission model as system-wide perf end up writing partial
> copies of this code. Let's instead export these properly so that modules
> can call them.
>
> Commit 5e9629d0ae97 ("drivers/perf: arm_spe: Use perf_allow_kernel()
> for permissions") already moved perf_allow_kernel() out of line and
> exported it. Patch 1 does the same for the other two, and provides
> !CONFIG_PERF_EVENTS stubs so the helpers stay callable when perf is
> compiled out.
>
> Patch 2 converts drm/xe's OA and EU stall paths to call
> perf_allow_cpu(), so xe observation now respects the system
> perf_event_paranoid policy and consults the LSM hook. Sites that have
> already configured an LSM perf policy or tuned the paranoid sysctl will
> now see those settings honored on xe as well.
>
> Changes since v1:
>
> * Patch 1: add !CONFIG_PERF_EVENTS stubs that fall back to
> perfmon_capable() so the helpers remain callable when perf is
> compiled out. The sashiko-bot AI review caught that the v1 code
> would otherwise fail to build with PERF_EVENTS=n.
>
> John Hubbard (2):
> perf/core: out-of-line and export perf_allow_cpu/tracepoint()
> drm/xe: gate observation streams with perf_allow_cpu()
>
> drivers/gpu/drm/xe/xe_eu_stall.c | 5 +++--
> drivers/gpu/drm/xe/xe_oa.c | 25 +++++++++++++---------
> drivers/gpu/drm/xe/xe_observation.c | 32 ++++++++++++++++++++++++-----
> drivers/gpu/drm/xe/xe_observation.h | 3 +--
> include/linux/perf_event.h | 31 ++++++++++++++--------------
> kernel/events/core.c | 18 ++++++++++++++++
> 6 files changed, 79 insertions(+), 35 deletions(-)
Sure, works for me. How do you want to route these things, Xe tree or
-tip?
next prev parent reply other threads:[~2026-05-23 8:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 1:33 [PATCH v2 0/2] complete perf_allow_* trio and use in drm/xe John Hubbard
2026-05-23 1:33 ` [PATCH v2 1/2] perf/core: out-of-line and export perf_allow_cpu/tracepoint() John Hubbard
2026-05-23 1:51 ` sashiko-bot
2026-05-23 2:07 ` John Hubbard
2026-05-27 3:34 ` Dixit, Ashutosh
2026-05-23 1:33 ` [PATCH v2 2/2] drm/xe: gate observation streams with perf_allow_cpu() John Hubbard
2026-05-23 2:20 ` sashiko-bot
2026-05-23 2:24 ` John Hubbard
2026-05-27 3:34 ` Dixit, Ashutosh
2026-05-23 8:40 ` Peter Zijlstra [this message]
2026-05-23 17:52 ` [PATCH v2 0/2] complete perf_allow_* trio and use in drm/xe John Hubbard
2026-05-27 3:34 ` Dixit, Ashutosh
2026-05-27 15:42 ` Rodrigo Vivi
2026-05-27 16:30 ` Peter Zijlstra
2026-05-27 23:00 ` Dixit, Ashutosh
2026-05-28 0:24 ` John Hubbard
2026-05-28 15:24 ` Dixit, Ashutosh
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=20260523084056.GE3102624@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=airlied@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jhubbard@nvidia.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthew.brost@intel.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.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