From: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
To: amd-gfx@lists.freedesktop.org, 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>,
"Tvrtko Ursulin" <tvrtko.ursulin@igalia.com>
Subject: [RFC 0/3] Simpler and more consistent handling of entities on missing hw blocks
Date: Wed, 7 Jan 2026 12:43:48 +0000 [thread overview]
Message-ID: <20260107124351.94738-1-tvrtko.ursulin@igalia.com> (raw)
Trying to consolidate how entity creation and/or submission is rejected when
underlying hw ip block is missing.
Amdgpu appears to be the only user which can pass zero schedulers, or a single
NULL scheduler to drm_sched_entity_init(), so if I did not miss something subtle
and the first two patches are okay, then the last one removes handling for that
special case from the DRM scheduler.
Tvrtko Ursulin (3):
drm/amdgpu: Reject impossible entities early
drm/amdgpu: Remove redundant missing hw ip handling
drm/sched: Disallow initializing entities with no schedulers
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 7 -------
drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c | 5 +++++
drivers/gpu/drm/scheduler/sched_entity.c | 13 ++++---------
3 files changed, 9 insertions(+), 16 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-07 12:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 12:43 Tvrtko Ursulin [this message]
2026-01-07 12:43 ` [RFC 1/3] drm/amdgpu: Reject impossible entities early Tvrtko Ursulin
2026-01-08 13:13 ` Christian König
2026-01-07 12:43 ` [RFC 2/3] drm/amdgpu: Remove redundant missing hw ip handling Tvrtko Ursulin
2026-03-03 14:36 ` Christian König
2026-01-07 12:43 ` [RFC 3/3] drm/sched: Disallow initializing entities with no schedulers Tvrtko Ursulin
2026-01-08 13:54 ` Philipp Stanner
2026-01-12 10:29 ` Tvrtko Ursulin
2026-01-12 11:33 ` Danilo Krummrich
2026-01-12 12:49 ` Philipp Stanner
2026-01-12 12:51 ` Christian König
2026-01-22 8:52 ` Tvrtko Ursulin
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=20260107124351.94738-1-tvrtko.ursulin@igalia.com \
--to=tvrtko.ursulin@igalia.com \
--cc=amd-gfx@lists.freedesktop.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 \
/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