[v2,0/8] DRM scheduler fixes, or not, or incorrect kind

Message

Tvrtko Ursulin Sept. 9, 2024, 5:19 p.m. UTC

From: Tvrtko Ursulin <[e-mail]>

Re-spin of the series from two days ago with review feedback addressed and
some new patches added.

Changelog is in individual patches but essentially new patches are renames
and struct members re-ordering as discussed in v1, plus one more optimisation
when I noticed we can save another spinlock re-lock cycle this time on rq->lock.

Cc: Christian König <[e-mail]>
Cc: Alex Deucher <[e-mail]>
Cc: Luben Tuikov <[e-mail]>
Cc: Matthew Brost <[e-mail]>
Cc: Philipp Stanner <[e-mail]>

Tvrtko Ursulin (8):
  drm/sched: Add locking to drm_sched_entity_modify_sched
  drm/sched: Always wake up correct scheduler in
    drm_sched_entity_push_job
  drm/sched: Always increment correct scheduler score
  drm/sched: Optimise drm_sched_entity_push_job
  drm/sched: Stop setting current entity in FIFO mode
  drm/sched: Re-order struct drm_sched_rq members for clarity
  drm/sched: Re-group and rename the entity run-queue lock
  drm/sched: Further optimise drm_sched_entity_push_job

 drivers/gpu/drm/scheduler/sched_entity.c | 40 +++++++++++------
 drivers/gpu/drm/scheduler/sched_main.c   | 57 ++++++++++++++----------
 include/drm/gpu_scheduler.h              | 31 +++++++------
 3 files changed, 77 insertions(+), 51 deletions(-)