diff options
| author | Philipp Stanner <phasta@kernel.org> | 2026-09-22 16:54:42 +0200 |
|---|---|---|
| committer | Philipp Stanner <phasta@kernel.org> | 2026-09-30 13:50:15 +0200 |
| commit | 4b7a49d66c8398a7984dff4ac54d1acc6b3a58df (patch) | |
| tree | a489e6ca7158e4349d70e0dab3c84e9b9e0d826f /tools/perf/scripts/python | |
| parent | aafd4205a75de54cb46458bbc70f35a0be1d7533 (diff) | |
| download | linux-4b7a49d66c8398a7984dff4ac54d1acc6b3a58df.tar.gz linux-4b7a49d66c8398a7984dff4ac54d1acc6b3a58df.zip | |
drm/sched: Protect entity->last_scheduled with spinlock
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.
Acked-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Philipp Stanner <phasta@kernel.org>
Link: https://patch.msgid.link/20260922145441.619097-2-phasta@kernel.org
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions