From: Philipp Stanner <phasta@mailbox.org>
To: Pierre-Eric Pelloux-Prayer <pierre-eric@damsy.net>,
Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com>,
Tvrtko Ursulin <tvrtko.ursulin@igalia.com>,
Philipp Stanner <phasta@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Matthew Brost <matthew.brost@intel.com>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
etnaviv@lists.freedesktop.org, freedreno@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, lima@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-arm-msm@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, nouveau@lists.freedesktop.org
Subject: Re: [PATCH v8 00/10] Improve gpu_scheduler trace events + UAPI
Date: Wed, 09 Apr 2025 10:03:34 +0200 [thread overview]
Message-ID: <2486e9eba3806f8e7fc3df724e916929a627fac7.camel@mailbox.org> (raw)
In-Reply-To: <f3416edf-46f8-4296-86bd-600ab629fe60@damsy.net>
On Wed, 2025-04-09 at 09:52 +0200, Pierre-Eric Pelloux-Prayer wrote:
> Hi,
>
> I've rebased the series on top of drm-next, applied the minor tweaks
> suggested by Tvrtko on v8 and
> the R-b tags. The result can be found on gitlab.fdo:
>
> https://gitlab.freedesktop.org/pepp/linux/-/commits/improve_gpu_scheduler_trace_v9
>
> I believe it's ready to be merged, unless I've missed something?
Has slipped my radar for a while, sorry.
I browsed over the series
Can you pro forma send the v9 (with the scheduler maintainers also in
the cover letter's CC) with the changelog, please?
Then I'd ACK and someone (probably me?) can take it in.
Thanks
P.
>
> Thanks,
> Pierre-Eric
>
> Le 20/03/2025 à 10:57, Pierre-Eric Pelloux-Prayer a écrit :
> > Hi,
> >
> > The initial goal of this series was to improve the drm and amdgpu
> > trace events to be able to expose more of the inner workings of
> > the scheduler and drivers to developers via tools.
> >
> > Then, the series evolved to become focused only on gpu_scheduler.
> > The changes around vblank events will be part of a different
> > series, as well as the amdgpu ones.
> >
> > Moreover Sima suggested to make some trace events stable uAPI,
> > so tools can rely on them long term.
> >
> > The first patches extend and cleanup the gpu scheduler events,
> > then add a documentation entry in drm-uapi.rst.
> >
> > The last 2 patches are new in v8. One is based on a suggestion
> > from Tvrtko and gets rid of drm_sched_job::id. The other is a
> > cleanup of amdgpu trace events to use the fence=%llu:%llu format.
> >
> > The drm_sched_job patches don't affect gpuvis which has code to
> > parse
> > the gpu_scheduler events but these events are not enabled.
> >
> > Changes since v7:
> > * uint64_t -> u64
> > * reworked dependencies tracing (Tvrtko)
> > * use common name prefix for all events (Tvrtko)
> > * dropped drm_sched_job::id (Tvrtko)
> >
> > Useful links:
> > - userspace tool using the updated events:
> > https://gitlab.freedesktop.org/tomstdenis/umr/-/merge_requests/37
> > - v7:
> > https://lists.freedesktop.org/archives/dri-devel/2025-January/488117.html
> >
> > Pierre-Eric Pelloux-Prayer (10):
> > drm/debugfs: output client_id in in drm_clients_info
> > drm/sched: store the drm client_id in drm_sched_fence
> > drm/sched: add device name to the drm_sched_process_job event
> > drm/sched: cleanup gpu_scheduler trace events
> > drm/sched: trace dependencies for gpu jobs
> > drm/sched: add the drm_client_id to the drm_sched_run/exec_job
> > events
> > drm/sched: cleanup event names
> > drm/doc: document some tracepoints as uAPI
> > drm: get rid of drm_sched_job::id
> > drm/amdgpu: update trace format to match gpu_scheduler_trace
> >
> > Documentation/gpu/drm-uapi.rst | 19 ++++
> > drivers/accel/amdxdna/aie2_ctx.c | 3 +-
> > drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c | 2 +-
> > drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 3 +-
> > drivers/gpu/drm/amd/amdgpu/amdgpu_job.c | 8 +-
> > drivers/gpu/drm/amd/amdgpu/amdgpu_job.h | 3 +-
> > drivers/gpu/drm/amd/amdgpu/amdgpu_trace.h | 32 ++----
> > drivers/gpu/drm/drm_debugfs.c | 10 +-
> > drivers/gpu/drm/etnaviv/etnaviv_gem_submit.c | 2 +-
> > drivers/gpu/drm/imagination/pvr_job.c | 2 +-
> > drivers/gpu/drm/imagination/pvr_queue.c | 5 +-
> > drivers/gpu/drm/imagination/pvr_queue.h | 2 +-
> > drivers/gpu/drm/lima/lima_gem.c | 2 +-
> > drivers/gpu/drm/lima/lima_sched.c | 6 +-
> > drivers/gpu/drm/lima/lima_sched.h | 3 +-
> > drivers/gpu/drm/msm/msm_gem_submit.c | 8 +-
> > drivers/gpu/drm/nouveau/nouveau_sched.c | 3 +-
> > drivers/gpu/drm/panfrost/panfrost_drv.c | 2 +-
> > drivers/gpu/drm/panthor/panthor_drv.c | 3 +-
> > drivers/gpu/drm/panthor/panthor_mmu.c | 2 +-
> > drivers/gpu/drm/panthor/panthor_sched.c | 5 +-
> > drivers/gpu/drm/panthor/panthor_sched.h | 3 +-
> > .../gpu/drm/scheduler/gpu_scheduler_trace.h | 103
> > +++++++++++++-----
> > drivers/gpu/drm/scheduler/sched_entity.c | 16 ++-
> > drivers/gpu/drm/scheduler/sched_fence.c | 4 +-
> > drivers/gpu/drm/scheduler/sched_internal.h | 2 +-
> > drivers/gpu/drm/scheduler/sched_main.c | 11 +-
> > drivers/gpu/drm/v3d/v3d_submit.c | 2 +-
> > drivers/gpu/drm/xe/xe_sched_job.c | 3 +-
> > include/drm/gpu_scheduler.h | 13 ++-
> > 30 files changed, 186 insertions(+), 96 deletions(-)
> >
prev parent reply other threads:[~2025-04-09 8:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 9:57 Pierre-Eric Pelloux-Prayer
2025-03-20 9:57 ` [PATCH v8 01/10] drm/debugfs: output client_id in in drm_clients_info Pierre-Eric Pelloux-Prayer
2025-03-20 9:57 ` [PATCH v8 02/10] drm/sched: store the drm client_id in drm_sched_fence Pierre-Eric Pelloux-Prayer
2025-03-20 9:57 ` [PATCH v8 03/10] drm/sched: add device name to the drm_sched_process_job event Pierre-Eric Pelloux-Prayer
2025-03-20 9:58 ` [PATCH v8 04/10] drm/sched: cleanup gpu_scheduler trace events Pierre-Eric Pelloux-Prayer
2025-03-20 10:46 ` Tvrtko Ursulin
2025-03-20 9:58 ` [PATCH v8 05/10] drm/sched: trace dependencies for gpu jobs Pierre-Eric Pelloux-Prayer
2025-03-20 10:47 ` Tvrtko Ursulin
2025-03-20 9:58 ` [PATCH v8 06/10] drm/sched: add the drm_client_id to the drm_sched_run/exec_job events Pierre-Eric Pelloux-Prayer
2025-04-09 7:56 ` Philipp Stanner
2025-03-20 9:58 ` [PATCH v8 07/10] drm/sched: cleanup event names Pierre-Eric Pelloux-Prayer
2025-03-20 10:49 ` Tvrtko Ursulin
2025-03-20 9:58 ` [PATCH v8 08/10] drm/doc: document some tracepoints as uAPI Pierre-Eric Pelloux-Prayer
2025-03-20 9:58 ` [PATCH v8 09/10] drm: get rid of drm_sched_job::id Pierre-Eric Pelloux-Prayer
2025-03-20 10:09 ` Christian König
2025-03-20 10:55 ` Tvrtko Ursulin
2025-03-20 9:58 ` [PATCH v8 10/10] drm/amdgpu: update trace format to match gpu_scheduler_trace Pierre-Eric Pelloux-Prayer
2025-03-20 10:09 ` Christian König
2025-04-09 7:52 ` [PATCH v8 00/10] Improve gpu_scheduler trace events + UAPI Pierre-Eric Pelloux-Prayer
2025-04-09 8:03 ` Philipp Stanner [this message]
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=2486e9eba3806f8e7fc3df724e916929a627fac7.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lima@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=nouveau@lists.freedesktop.org \
--cc=phasta@kernel.org \
--cc=pierre-eric.pelloux-prayer@amd.com \
--cc=pierre-eric@damsy.net \
--cc=tvrtko.ursulin@igalia.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
all inboxes | Powered by JetHome®