On Fri, 2026-10-02 at 13:46 +0100, Tvrtko Ursulin wrote: > When the out of range priority at entity init time is clamped to the > number of run queues in the supplied scheduler the internal run-queue > priority needs to be adjusted as well. > > There is no impact since none of the drivers hit the clamping path, but > we still need to address it by moving the entity->rq_priority assignment > to after the clamping is done. > > Note that a lot of this will hopefully get removed once again when the > single run-queue simplification lands. > > Signed-off-by: Tvrtko Ursulin <[email protected]> > Fixes: 2fa4d8e2c109 ("drm/sched: Add fair scheduling policy")
Help me out here; we recently landed this fix [1] that Luke reported. Is there a relation? I guess not, since you say there is "no impact". This did not exist before CFS in drm_sched, did it? Did you discover it by review? P. [1] https://lore.kernel.org/dri-devel/[email protected]/
