From: Matthew Brost <matthew.brost@intel.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: <dri-devel@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>, <alexdeucher@gmail.com>,
<dakr@kernel.org>, <pstanner@redhat.com>,
"Philipp Stanner" <phasta@kernel.org>
Subject: Re: [RFC PATCH 1/4] drm/sched: Add pending job list iterator
Date: Tue, 7 Oct 2025 01:09:34 -0700 [thread overview]
Message-ID: <aOTKvgqYFk8kw6Tm@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <be806a5e-75c9-45da-962f-2c1db75b4a07@amd.com>
On Tue, Oct 07, 2025 at 09:28:56AM +0200, Christian König wrote:
> On 02.10.25 07:16, Matthew Brost wrote:
> > Stop open coding pending job list in drivers. Add pending job list
> > iterator which safely walks DRM scheduler list either locklessly
> > asserting DRM scheduler is stopped or takes pending job list lock.
>
> Taking the job list lock and walking the pending list while the scheduler is not stopped is most likely a NO-GO.
>
I agree. But this patch doesn’t do that — it actually does the opposite.
It ensures that if you need to walk the scheduler list locklessly, the
scheduler is stopped at both the beginning and end of the iterator, or
it correctly takes the pending list lock.
So, what’s the issue? Or is there just some confusion about what this
patch is actually doing?
> As far as I understand it that is exactly what Philip rejected as looking into scheduler internals during the discussion on XDC.
>
I thought we agreed on having a well-defined iterator for walking the
pending list, ensuring correct usage, rather than having drivers walk
the pending list themselves. From my understanding, this is exactly what
we agreed upon.
> So why is that actually needed? For debugging or something functional?
>
Drivers inevitably need to walk the pending list during recovery flows
(such as resets, resubmissions, VF migration, etc.). This ensures that a
driver knows what it’s doing when it does so, and avoids directly
touching scheduler internals. Instead, it should just call
drm_sched_for_each_pending_job.
This has actually been helpful in Xe already — when I was working on
scheduler backend changes, it helped catch cases where I accidentally
flipped the stopped flag while walking the job list. Without this, it
could have randomly blown up later if a perfectly timed race condition
occured (e.g., free_job fired).
Matt
> Regards,
> Christian.
>
> >
> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > ---
> > include/drm/gpu_scheduler.h | 64 +++++++++++++++++++++++++++++++++++++
> > 1 file changed, 64 insertions(+)
> >
> > diff --git a/include/drm/gpu_scheduler.h b/include/drm/gpu_scheduler.h
> > index fb88301b3c45..a2dcabab8284 100644
> > --- a/include/drm/gpu_scheduler.h
> > +++ b/include/drm/gpu_scheduler.h
> > @@ -698,4 +698,68 @@ void drm_sched_entity_modify_sched(struct drm_sched_entity *entity,
> > struct drm_gpu_scheduler **sched_list,
> > unsigned int num_sched_list);
> >
> > +/* Inlines */
> > +
> > +/**
> > + * struct drm_sched_iter_pending_job - DRM scheduler pending job iterator state
> > + * @sched: DRM scheduler associated with pending job iterator
> > + * @stopped: DRM scheduler stopped state associated with pending job iterator
> > + */
> > +struct drm_sched_iter_pending_job {
> > + struct drm_gpu_scheduler *sched;
> > + bool stopped;
> > +};
> > +
> > +/* Drivers should never call this directly */
> > +static inline struct drm_sched_iter_pending_job
> > +__drm_sched_iter_pending_job_begin(struct drm_gpu_scheduler *sched, bool stopped)
> > +{
> > + struct drm_sched_iter_pending_job iter = {
> > + .sched = sched,
> > + .stopped = stopped,
> > + };
> > +
> > + if (stopped)
> > + WARN_ON(!READ_ONCE(sched->pause_submit));
> > + else
> > + spin_lock(&sched->job_list_lock);
> > +
> > + return iter;
> > +}
> > +
> > +/* Drivers should never call this directly */
> > +static inline void
> > +__drm_sched_iter_pending_job_end(const struct drm_sched_iter_pending_job iter)
> > +{
> > + if (iter.stopped)
> > + WARN_ON(!READ_ONCE(iter.sched->pause_submit));
> > + else
> > + spin_unlock(&iter.sched->job_list_lock);
> > +}
> > +
> > +DEFINE_CLASS(drm_sched_iter_pending_job, struct drm_sched_iter_pending_job,
> > + __drm_sched_iter_pending_job_end(_T);,
> > + __drm_sched_iter_pending_job_begin(__sched, __stopped),
> > + struct drm_gpu_scheduler * __sched, bool __stopped);
> > +static inline void
> > +*class_drm_sched_iter_pending_job_lock_ptr(class_drm_sched_iter_pending_job_t *_T)
> > +{return _T; }
> > +#define class_drm_sched_iter_pending_job_is_conditional false
> > +
> > +/**
> > + * drm_sched_for_each_pending_job() - Iterator for each pending job in scheduler
> > + * @__job: Current pending job being iterated over
> > + * @__sched: DRM scheduler to iterate over pending jobs
> > + * @__entity: DRM scheduler entity to filter jobs, NULL indicates no filter
> > + * @__stopped: DRM scheduler stopped state
> > + *
> > + * Iterator for each pending job in scheduler, filtering on an entity, and
> > + * enforcing locking rules (either scheduler fully stoppped or correctly takes
> > + * job_list_lock).
> > + */
> > +#define drm_sched_for_each_pending_job(__job, __sched, __entitiy, __stopped) \
> > + scoped_guard(drm_sched_iter_pending_job, __sched, __stopped) \
> > + list_for_each_entry(__job, &(__sched)->pending_list, list) \
> > + for_each_if(!__entitiy || (__job)->entity == (__entitiy))
> > +
> > #endif
>
next prev parent reply other threads:[~2025-10-07 8:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 5:16 [RFC PATCH 0/4] Fix DRM scheduler layering violations in Xe Matthew Brost
2025-10-02 5:16 ` [RFC PATCH 1/4] drm/sched: Add pending job list iterator Matthew Brost
2025-10-07 7:28 ` Christian König
2025-10-07 8:09 ` Matthew Brost [this message]
2025-10-07 8:28 ` Matthew Brost
2025-10-07 8:44 ` Christian König
2025-10-07 9:44 ` Matthew Brost
2025-10-07 9:51 ` Danilo Krummrich
2025-10-02 5:16 ` [RFC PATCH 2/4] drm/sched: Add several job helpers to avoid drivers touching scheduler state Matthew Brost
2025-10-02 5:16 ` [RFC PATCH 3/4] drm/xe: Add dedicated message lock Matthew Brost
2025-10-02 5:16 ` [RFC PATCH 4/4] drm/xe: Stop abusing DRM scheduler internals Matthew Brost
2025-10-02 6:01 ` ✗ CI.checkpatch: warning for Fix DRM scheduler layering violations in Xe Patchwork
2025-10-02 6:02 ` ✓ CI.KUnit: success " Patchwork
2025-10-02 6:38 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-02 7:58 ` ✗ 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=aOTKvgqYFk8kw6Tm@lstrano-desk.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=alexdeucher@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=phasta@kernel.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