On Tue, 2026-09-22 at 16:54 +0200, Philipp Stanner wrote:
> The entity->last_scheduled field has always been set and read with
> special RCU functions in addition to memory barriers.
>
> This was added in
>
> commit 70102d77ff22 ("drm/scheduler: add drm_sched_entity_error and use rcu
> for last_scheduled")
>
> however, no proper justification for that mechanism was provided. There
> seems to be no obvious reason, since the entity lock is available and
> taken at all places that evaluate the last_scheduled field. The only
> exception is drm_sched_entity_error(), which is not performance critical
> in any way.
>
> Improve robustness, readability and maintainability by replacing RCU and
> barriers with the lock.
>
> Signed-off-by: Philipp Stanner <[email protected]>
> Acked-by: Christian König <[email protected]>
Applied that to misc-next.
P.
