From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: niranjana.vishwanathapura@intel.com, christian.koenig@amd.com,
pstanner@redhat.com, dakr@kernel.org
Subject: [PATCH v9 0/2] Add DRM sched support functions to avoid driver side layering violations
Date: Tue, 9 Dec 2025 12:00:37 -0800 [thread overview]
Message-ID: <20251209200039.1366764-1-matthew.brost@intel.com> (raw)
Subset of [1], believe we are in agreement these can go into the DRM
scheduler. Will post the Xe in a follow once patches make it from
drm-misc-next to drm-xe-next.
Leaving todo.rst as is with respect to resubmit, as I believe we still
have long-term plans to change job tracking to scheduler fence tracking.
If we go in that direction, the iterator in this series can be converted
to a fence-based iterator. If needed, todo.rst can also be updated in a
follow-up patch, but for functionality and cleanups on the Xe driver
side, it would be good to get this code in.
Matt
[1] https://patchwork.freedesktop.org/series/155314/
Matthew Brost (2):
drm/sched: Add several job helpers to avoid drivers touching scheduler
state
drm/sched: Add pending job list iterator
drivers/gpu/drm/scheduler/sched_main.c | 40 ++++++++++++++++++--
include/drm/gpu_scheduler.h | 52 ++++++++++++++++++++++++++
2 files changed, 89 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2025-12-09 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 20:00 Matthew Brost [this message]
2025-12-09 20:00 ` [PATCH v9 1/2] drm/sched: Add several job helpers to avoid drivers touching scheduler state Matthew Brost
2025-12-09 20:00 ` [PATCH v9 2/2] drm/sched: Add pending job list iterator Matthew Brost
2025-12-10 10:38 ` ✗ CI.checkpatch: warning for Add DRM sched support functions to avoid driver side layering violations (rev2) Patchwork
2025-12-10 10:39 ` ✓ CI.KUnit: success " Patchwork
2025-12-10 11:50 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-10 16:33 ` ✗ Xe.CI.Full: failure " 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=20251209200039.1366764-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=niranjana.vishwanathapura@intel.com \
--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