From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: John Hubbard <jhubbard@nvidia.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
"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: Tue, 26 May 2026 20:34:57 -0700 [thread overview]
Message-ID: <87ecixv82m.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <8871a158-7a68-4247-a09f-bb3d970d6dc2@nvidia.com>
On Sat, 23 May 2026 10:52:16 -0700, John Hubbard wrote:
>
> On 5/23/26 1:40 AM, Peter Zijlstra wrote:
> > On Fri, May 22, 2026 at 06:33:24PM -0700, John Hubbard wrote:
> ...
> >> 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?
>
> Hi Peter,
>
> Maybe -tip, but really, either way is perfectly OK with me.
I've R-b'd both the patches. If you want to merge via Xe tree, let me know
and we can get them merged.
Thanks.
--
Ashutosh
next prev parent reply other threads:[~2026-05-27 3:34 UTC|newest]
Thread overview: 14+ 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 ` [PATCH v2 0/2] complete perf_allow_* trio and use in drm/xe Peter Zijlstra
2026-05-23 17:52 ` John Hubbard
2026-05-27 3:34 ` Dixit, Ashutosh [this message]
2026-05-27 15:42 ` Rodrigo Vivi
2026-05-27 16:30 ` Peter Zijlstra
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=87ecixv82m.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--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=peterz@infradead.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