Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: christian.koenig@amd.com, pstanner@redhat.com, dakr@kernel.org
Subject: [RFC PATCH v2 0/4] Fix DRM scheduler layering violations in Xe
Date: Fri,  3 Oct 2025 13:11:52 -0700	[thread overview]
Message-ID: <20251003201156.1995113-1-matthew.brost@intel.com> (raw)

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.

This is being sent as an RFC since only Xe is updated in this series. If
consensus is reached, a follow-up series can address other drivers in
the subsystem.

v2:
 - Fix checkpatch / naming issues

Matt

Matthew Brost (4):
  drm/sched: Add pending job list iterator
  drm/sched: Add several job helpers to avoid drivers touching scheduler
    state
  drm/xe: Add dedicated message lock
  drm/xe: Stop abusing DRM scheduler internals

 drivers/gpu/drm/xe/xe_gpu_scheduler.c       |   3 +-
 drivers/gpu/drm/xe/xe_gpu_scheduler.h       |  31 ++----
 drivers/gpu/drm/xe/xe_gpu_scheduler_types.h |   2 +
 drivers/gpu/drm/xe/xe_guc_submit.c          |  34 +++---
 drivers/gpu/drm/xe/xe_guc_submit_types.h    |   1 -
 include/drm/gpu_scheduler.h                 | 116 ++++++++++++++++++++
 6 files changed, 142 insertions(+), 45 deletions(-)

-- 
2.34.1


             reply	other threads:[~2025-10-03 20:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03 20:11 Matthew Brost [this message]
2025-10-03 20:11 ` [RFC PATCH v2 1/4] drm/sched: Add pending job list iterator Matthew Brost
2025-10-06  9:19   ` Jani Nikula
2025-10-06 13:17     ` Matthew Brost
2025-10-03 20:11 ` [RFC PATCH v2 2/4] drm/sched: Add several job helpers to avoid drivers touching scheduler state Matthew Brost
2025-10-03 20:11 ` [RFC PATCH v2 3/4] drm/xe: Add dedicated message lock Matthew Brost
2025-10-03 20:11 ` [RFC PATCH v2 4/4] drm/xe: Stop abusing DRM scheduler internals Matthew Brost
2025-10-03 20:17 ` ✗ CI.checkpatch: warning for Fix DRM scheduler layering violations in Xe (rev2) Patchwork
2025-10-03 20:19 ` ✓ CI.KUnit: success " Patchwork
2025-10-03 20:54 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-03 22:52 ` ✓ Xe.CI.Full: " Patchwork

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=20251003201156.1995113-1-matthew.brost@intel.com \
    --to=matthew.brost@intel.com \
    --cc=christian.koenig@amd.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=pstanner@redhat.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