From: Philipp Stanner <phasta@mailbox.org>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
tvrtko.ursulin@igalia.com, dakr@kernel.org,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/sched: add drm_sched_prealloc_dependency_slots v2
Date: Wed, 09 Apr 2025 12:28:37 +0200 [thread overview]
Message-ID: <867c3abac8a222fa42921a6725e85fe459bc9d5e.camel@mailbox.org> (raw)
In-Reply-To: <20250321155852.15162-1-christian.koenig@amd.com>
On Fri, 2025-03-21 at 16:58 +0100, Christian König wrote:
> Sometimes drivers need to be able to submit multiple jobs which
> depend on
> each other to different schedulers at the same time, but using
> drm_sched_job_add_dependency() can't fail any more after the first
> job is
> initialized.
>
> This function preallocate memory for dependency slots so that no
> ENOMEM
> can come later while adding dependencies.
>
> v2: rework implementation an documentation
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/scheduler/sched_main.c | 44
> ++++++++++++++++++++++++--
> include/drm/gpu_scheduler.h | 2 ++
> 2 files changed, 43 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/scheduler/sched_main.c
> b/drivers/gpu/drm/scheduler/sched_main.c
> index 4d4219fbe49d..ee3701f346b2 100644
> --- a/drivers/gpu/drm/scheduler/sched_main.c
> +++ b/drivers/gpu/drm/scheduler/sched_main.c
> @@ -852,6 +852,39 @@ void drm_sched_job_arm(struct drm_sched_job
> *job)
> }
> EXPORT_SYMBOL(drm_sched_job_arm);
>
> +/**
> + * drm_sched_job_prealloc_dependency_slots - avoid ENOMEM on adding
> dependencies
> + * @job: scheduler job where dependencies will be added
> + * @num_deps: number of dependencies to preallocate slots for
> + *
> + * Sometimes drivers need to be able to submit multiple jobs which
> depend on
> + * each other to different schedulers at the same time, but using
> + * drm_sched_job_add_dependency() can't fail any more after the
> first job is
> + * initialized.
> + *
> + * This function preallocate memory for dependency slots so that no
> ENOMEM can
> + * come later while adding dependencies.
> + *
> + * Return:
> + * 0 on success, or an error on failing to expand the array.
> + */
> +int drm_sched_job_prealloc_dependency_slots(struct drm_sched_job
> *job,
> + unsigned int num_deps)
> +{
> + u32 id = 0;
> + int ret;
> +
> + while (num_deps--) {
> + ret = xa_alloc(&job->dependencies, &id,
> XA_ZERO_ENTRY,
> + xa_limit_32b, GFP_KERNEL);
I've had some time to re-read the xarray documentation and I think that
this is what xa_reserve() was born for. The Book of Documentation/core-
api/xarray.rst sayeth:
"Sometimes you need to ensure that a subsequent call to xa_store()
will not need to allocate memory. The xa_reserve() function
will store a reserved entry at the indicated index. Users of the
normal API will see this entry as containing ``NULL``."
That's far better, this way we don't have to use that more or less
xarray-internal flag.
> + if (ret != 0)
> + return ret;
> + }
> +
> + return 0;
> +}
> +EXPORT_SYMBOL(drm_sched_job_prealloc_dependency_slots);
> +
> /**
> * drm_sched_job_add_dependency - adds the fence as a job dependency
> * @job: scheduler job to add the dependencies to
> @@ -878,10 +911,15 @@ int drm_sched_job_add_dependency(struct
> drm_sched_job *job,
> * engines involved, rather than the number of BOs.
> */
> xa_for_each(&job->dependencies, index, entry) {
> - if (entry->context != fence->context)
> + if (xa_is_zero(entry)) {
> + /*
> + * Reserved entries must not alloc memory,
> but let's
> + * use GFP_ATOMIC just to be on the
> defensive side.
> + */
> + xa_store(&job->dependencies, index, fence,
> GFP_ATOMIC);
And regarding this – it can actually never happen, but you provide
ATOMIC just to be sure?
I think it would be better if we'd just run into an obvious bug here
instead, so like a deadlock with GFP_KERNEL.
That's how we do it with pointers that cannot be NULL, too. If the
impossible were to happen and it were NULL, we'd crash.
P.
> + } else if (entry->context != fence->context) {
> continue;
> -
> - if (dma_fence_is_later(fence, entry)) {
> + } else if (dma_fence_is_later(fence, entry)) {
> dma_fence_put(entry);
> xa_store(&job->dependencies, index, fence,
> GFP_KERNEL);
> } else {
> diff --git a/include/drm/gpu_scheduler.h
> b/include/drm/gpu_scheduler.h
> index 1a7e377d4cbb..916e820b27ff 100644
> --- a/include/drm/gpu_scheduler.h
> +++ b/include/drm/gpu_scheduler.h
> @@ -632,6 +632,8 @@ int drm_sched_job_init(struct drm_sched_job *job,
> u32 credits, void *owner);
> void drm_sched_job_arm(struct drm_sched_job *job);
> void drm_sched_entity_push_job(struct drm_sched_job *sched_job);
> +int drm_sched_job_prealloc_dependency_slots(struct drm_sched_job
> *job,
> + unsigned int num_deps);
> int drm_sched_job_add_dependency(struct drm_sched_job *job,
> struct dma_fence *fence);
> int drm_sched_job_add_syncobj_dependency(struct drm_sched_job *job,
next prev parent reply other threads:[~2025-04-10 13:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 15:58 [PATCH 1/2] drm/sched: add drm_sched_prealloc_dependency_slots v2 Christian König
2025-03-21 15:58 ` [PATCH 2/2] drm/amdgpu: fix gang submission error handling Christian König
2025-03-24 8:38 ` Tvrtko Ursulin
2025-03-21 18:05 ` [PATCH 1/2] drm/sched: add drm_sched_prealloc_dependency_slots v2 Philipp Stanner
2025-03-24 12:59 ` Christian König
2025-03-24 8:35 ` Tvrtko Ursulin
2025-03-24 13:01 ` Christian König
2025-04-09 10:28 ` Philipp Stanner [this message]
2025-04-09 13:55 ` Christian König
2025-04-09 14:04 ` Philipp Stanner
2025-04-14 12:48 ` Philipp Stanner
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=867c3abac8a222fa42921a6725e85fe459bc9d5e.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=phasta@kernel.org \
--cc=tvrtko.ursulin@igalia.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