From: Philipp Stanner <phasta@mailbox.org>
To: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>,
dri-devel@lists.freedesktop.org
Cc: kernel-dev@igalia.com,
"Christian König" <christian.koenig@amd.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Matthew Brost" <matthew.brost@intel.com>,
"Philipp Stanner" <phasta@kernel.org>
Subject: Re: [PATCH] drm/sched: Remove mention of indirect buffers
Date: Thu, 28 Aug 2025 10:10:21 +0200 [thread overview]
Message-ID: <1b47130e1718a2b42e68a62dd469b81591d78901.camel@mailbox.org> (raw)
In-Reply-To: <20250814133627.2550-1-tvrtko.ursulin@igalia.com>
On Thu, 2025-08-14 at 14:36 +0100, Tvrtko Ursulin wrote:
> Indirect buffers are an AMD term describing essentialy a job submitted to
> the scheduler, just a lower level one. Since scheduler was promoted to be
> generic long ago, lets replace those references with jobs.
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
> Cc: Christian König <christian.koenig@amd.com>
> Cc: Danilo Krummrich <dakr@kernel.org>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: Philipp Stanner <phasta@kernel.org>
Applied to drm-misc-next
Thx
P.
> ---
> drivers/gpu/drm/scheduler/sched_entity.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/scheduler/sched_entity.c b/drivers/gpu/drm/scheduler/sched_entity.c
> index 8867b95ab089..254932b9050e 100644
> --- a/drivers/gpu/drm/scheduler/sched_entity.c
> +++ b/drivers/gpu/drm/scheduler/sched_entity.c
> @@ -285,9 +285,9 @@ long drm_sched_entity_flush(struct drm_sched_entity *entity, long timeout)
> return 0;
>
> sched = entity->rq->sched;
> - /**
> - * The client will not queue more IBs during this fini, consume existing
> - * queued IBs or discard them on SIGKILL
> + /*
> + * The client will not queue more jobs during this fini - consume
> + * existing queued ones, or discard them on SIGKILL.
> */
> if (current->flags & PF_EXITING) {
> if (timeout)
> @@ -300,7 +300,7 @@ long drm_sched_entity_flush(struct drm_sched_entity *entity, long timeout)
> drm_sched_entity_is_idle(entity));
> }
>
> - /* For killed process disable any more IBs enqueue right now */
> + /* For a killed process disallow further enqueueing of jobs. */
> last_user = cmpxchg(&entity->last_user, current->group_leader, NULL);
> if ((!last_user || last_user == current->group_leader) &&
> (current->flags & PF_EXITING) && (current->exit_code == SIGKILL))
> @@ -324,9 +324,9 @@ EXPORT_SYMBOL(drm_sched_entity_flush);
> void drm_sched_entity_fini(struct drm_sched_entity *entity)
> {
> /*
> - * If consumption of existing IBs wasn't completed. Forcefully remove
> - * them here. Also makes sure that the scheduler won't touch this entity
> - * any more.
> + * If consumption of existing jobs wasn't completed forcefully remove
> + * them. Also makes sure that the scheduler won't touch this entity any
> + * more.
> */
> drm_sched_entity_kill(entity);
>
prev parent reply other threads:[~2025-08-28 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 13:36 [PATCH] drm/sched: Remove mention of indirect buffers Tvrtko Ursulin
2025-08-14 13:38 ` Alex Deucher
2025-08-14 14:09 ` Christian König
2025-08-28 8:10 ` Philipp Stanner [this message]
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=1b47130e1718a2b42e68a62dd469b81591d78901.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-dev@igalia.com \
--cc=matthew.brost@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).