Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>,
	intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: christian.koenig@amd.com, pstanner@redhat.com, dakr@kernel.org
Subject: Re: [RFC PATCH v2 1/4] drm/sched: Add pending job list iterator
Date: Mon, 06 Oct 2025 12:19:29 +0300	[thread overview]
Message-ID: <d95920d45821d0e1e73737889e3e1481102c2e3b@intel.com> (raw)
In-Reply-To: <20251003201156.1995113-2-matthew.brost@intel.com>

On Fri, 03 Oct 2025, Matthew Brost <matthew.brost@intel.com> 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.
>
> v2:
>  - Fix checkpatch (CI)
>
> 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..bb49d8b715eb 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 */

Do they need to be inlines for perf reasons? Otherwise, inlines just
make proper encapsulation harder, proliferate header interdependencies,
and make the incremental builds slower.

Have you tried running the header through the compiler to see if it's
self-contained?

Unfortunately, DRM_HEADER_TEST still depends on BROKEN so we don't get
that check as part of the build. :(

BR,
Jani.


> +
> +/**
> + * struct drm_sched_pending_job_iter - 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_pending_job_iter {
> +	struct drm_gpu_scheduler *sched;
> +	bool stopped;
> +};
> +
> +/* Drivers should never call this directly */
> +static inline struct drm_sched_pending_job_iter
> +__drm_sched_pending_job_iter_begin(struct drm_gpu_scheduler *sched, bool stopped)
> +{
> +	struct drm_sched_pending_job_iter 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_pending_job_iter_end(const struct drm_sched_pending_job_iter iter)
> +{
> +	if (iter.stopped)
> +		WARN_ON(!READ_ONCE(iter.sched->pause_submit));
> +	else
> +		spin_unlock(&iter.sched->job_list_lock);
> +}
> +
> +DEFINE_CLASS(drm_sched_pending_job_iter, struct drm_sched_pending_job_iter,
> +	     __drm_sched_pending_job_iter_end(_T),
> +	     __drm_sched_pending_job_iter_begin(__sched, __stopped),
> +	     struct drm_gpu_scheduler *__sched, bool __stopped);
> +static inline void
> +*class_drm_sched_pending_job_iter_lock_ptr(class_drm_sched_pending_job_iter_t *_T)
> +{return _T; }
> +#define class_drm_sched_pending_job_iter_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 stopped or correctly takes
> + * job_list_lock).
> + */
> +#define drm_sched_for_each_pending_job(__job, __sched, __entity, __stopped)	\
> +	scoped_guard(drm_sched_pending_job_iter, (__sched), (__stopped))	\
> +		list_for_each_entry((__job), &(__sched)->pending_list, list)	\
> +			for_each_if(!(__entity) || (__job)->entity == (__entity))
> +
>  #endif

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-10-06  9:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03 20:11 [RFC PATCH v2 0/4] Fix DRM scheduler layering violations in Xe Matthew Brost
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 [this message]
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=d95920d45821d0e1e73737889e3e1481102c2e3b@intel.com \
    --to=jani.nikula@linux.intel.com \
    --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=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