From: Philipp Stanner <phasta@mailbox.org>
To: Matthew Brost <matthew.brost@intel.com>, intel-xe@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, phasta@kernel.org,
christian.koenig@amd.com, dakr@kernel.org
Subject: Re: [PATCH v7 0/9] Fix DRM scheduler layering violations in Xe
Date: Wed, 03 Dec 2025 09:33:09 +0100 [thread overview]
Message-ID: <591842211d77122faec79530c3d4d805cf09fe02.camel@mailbox.org> (raw)
In-Reply-To: <aS+RIfD3mb7dAHRV@lstrano-desk.jf.intel.com>
On Tue, 2025-12-02 at 17:23 -0800, Matthew Brost wrote:
> On Mon, Dec 01, 2025 at 10:39:45AM -0800, Matthew Brost wrote:
>
> Fellow DRM sched maintainers - going to merge the first two patches in
> this series to drm-misc-next two days from now unless I hear an
> objection.
Fellow maintainer Matt, it seems that none of us has ever been on Cc
for this series or patch? I can't find it in my inbox. Did you forget
to add us for 7 revisions, or did you omit us on purpose?
I look occasionally at dri-devel, but you know how huge the list is.
P.
>
> Matt
>
> > At XDC, we discussed that drivers should avoid accessing DRM scheduler
> > internals, misusing DRM scheduler locks, and adopt a well-defined
> > pending job list iterator. This series proposes the necessary changes to
> > the DRM scheduler to bring Xe in line with that agreement and updates Xe
> > to use the new DRM scheduler API.
> >
> > While here, cleanup LR queue handling and simplify GuC state machine in
> > Xe too. Also rework LRC timestamp sampling to avoid scheduling toggle.
> >
> > v2:
> > - Fix checkpatch / naming issues
> > v3:
> > - Only allow pending job list iterator to be called on stopped schedulers
> > - Cleanup LR queue handling / fix a few misselanous Xe scheduler issues
> > v4:
> > - Address Niranjana's feedback
> > - Add patch to avoid toggling scheduler state in the TDR
> > v5:
> > - Rebase
> > - Fixup LRC timeout check (Umesh)
> > v6:
> > - Fix VF bugs (Testing)
> > v7:
> > - Disable timestamp WA on VF
> >
> > Matt
> >
> > Matthew Brost (9):
> > drm/sched: Add several job helpers to avoid drivers touching scheduler
> > state
> > drm/sched: Add pending job list iterator
> > drm/xe: Add dedicated message lock
> > drm/xe: Stop abusing DRM scheduler internals
> > drm/xe: Only toggle scheduling in TDR if GuC is running
> > drm/xe: Do not deregister queues in TDR
> > drm/xe: Remove special casing for LR queues in submission
> > drm/xe: Disable timestamp WA on VFs
> > drm/xe: Avoid toggling schedule state to check LRC timestamp in TDR
> >
> > drivers/gpu/drm/scheduler/sched_main.c | 4 +-
> > drivers/gpu/drm/xe/xe_gpu_scheduler.c | 9 +-
> > drivers/gpu/drm/xe/xe_gpu_scheduler.h | 37 +-
> > drivers/gpu/drm/xe/xe_gpu_scheduler_types.h | 2 +
> > drivers/gpu/drm/xe/xe_guc_exec_queue_types.h | 2 -
> > drivers/gpu/drm/xe/xe_guc_submit.c | 362 +++----------------
> > drivers/gpu/drm/xe/xe_guc_submit_types.h | 11 -
> > drivers/gpu/drm/xe/xe_hw_fence.c | 16 -
> > drivers/gpu/drm/xe/xe_hw_fence.h | 2 -
> > drivers/gpu/drm/xe/xe_lrc.c | 45 ++-
> > drivers/gpu/drm/xe/xe_lrc.h | 3 +-
> > drivers/gpu/drm/xe/xe_ring_ops.c | 25 +-
> > drivers/gpu/drm/xe/xe_sched_job.c | 1 +
> > drivers/gpu/drm/xe/xe_sched_job_types.h | 2 +
> > drivers/gpu/drm/xe/xe_trace.h | 5 -
> > include/drm/gpu_scheduler.h | 82 +++++
> > 16 files changed, 211 insertions(+), 397 deletions(-)
> >
> > --
> > 2.34.1
> >
prev parent reply other threads:[~2025-12-03 8:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 18:39 [PATCH v7 0/9] Fix DRM scheduler layering violations in Xe Matthew Brost
2025-12-01 18:39 ` [PATCH v7 1/9] drm/sched: Add several job helpers to avoid drivers touching scheduler state Matthew Brost
2025-12-03 8:56 ` Philipp Stanner
2025-12-03 21:10 ` Matthew Brost
2025-12-01 18:39 ` [PATCH v7 2/9] drm/sched: Add pending job list iterator Matthew Brost
2025-12-03 9:07 ` Philipp Stanner
2025-12-03 10:28 ` Philipp Stanner
2025-12-04 16:04 ` Alex Deucher
2025-12-05 9:19 ` Christian König
2025-12-05 18:54 ` Matthew Brost
2025-12-08 13:33 ` Philipp Stanner
2025-12-01 18:39 ` [PATCH v7 3/9] drm/xe: Add dedicated message lock Matthew Brost
2025-12-03 9:38 ` Philipp Stanner
2025-12-01 18:39 ` [PATCH v7 4/9] drm/xe: Stop abusing DRM scheduler internals Matthew Brost
2025-12-03 10:56 ` Philipp Stanner
2025-12-03 20:44 ` Matthew Brost
2025-12-08 13:44 ` Philipp Stanner
2025-12-01 18:39 ` [PATCH v7 5/9] drm/xe: Only toggle scheduling in TDR if GuC is running Matthew Brost
2025-12-01 18:39 ` [PATCH v7 6/9] drm/xe: Do not deregister queues in TDR Matthew Brost
2025-12-01 18:39 ` [PATCH v7 7/9] drm/xe: Remove special casing for LR queues in submission Matthew Brost
2025-12-01 18:39 ` [PATCH v7 8/9] drm/xe: Disable timestamp WA on VFs Matthew Brost
2025-12-02 6:42 ` Umesh Nerlige Ramappa
2025-12-01 18:39 ` [PATCH v7 9/9] drm/xe: Avoid toggling schedule state to check LRC timestamp in TDR Matthew Brost
2025-12-02 7:31 ` Umesh Nerlige Ramappa
2025-12-02 15:14 ` Matthew Brost
2025-12-03 1:23 ` [PATCH v7 0/9] Fix DRM scheduler layering violations in Xe Matthew Brost
2025-12-03 8:33 ` 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=591842211d77122faec79530c3d4d805cf09fe02.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=phasta@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).