drm/ttm/tests: Let ttm_bo_test consider different ww_mutex implementation.
Subsystems (3)
PATCH 1/1 drm/ttm/tests: Let ttm_bo_test consider different ww_mutex implementation.
PREEMPT_RT has a different locking implementation for ww_mutex. The base mutex of struct ww_mutex is declared as struct WW_MUTEX_BASE. The latter is defined as mutex' for non-PREEMPT_RT builds and rt_mutex' for PREEMPT_RT builds.
Using mutex_lock() directly on the base mutex in ttm_bo_reserve_deadlock() leads to compile error on PREEMPT_RT.
The locking-selftest has its own defines to deal with this and it is probably best to defines the needed one within the test program since their usefulness is limited outside of well known selftests.
Provide ww_mutex_base_lock() which points to the correct function for PREEMPT_RT and non-PREEMPT_RT builds.
---
For the record, testing led to
| WARNING: CPU: 5 PID: 2089 at include/drm/ttm/ttm_bo.h:247 ttm_bo_reserve_no_wait_ticket+0xe8/0x150 [ttm_bo_test]
but this occurred with and without RT on v6.9-rc2.
drivers/gpu/drm/ttm/tests/ttm_bo_test.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
drivers/gpu/drm/ttm/tests/ttm_bo_test.c +7 -1
@@ -18,6 +18,12 @@#define BO_SIZE SZ_8K +#ifdef CONFIG_PREEMPT_RT +#define ww_mutex_base_lock (b) rt_mutex_lock(b) +#else +#define ww_mutex_base_lock (b) mutex_lock(b) +#endif +struct ttm_bo_test_case {const char *description;bool interruptible;
@@ -142,7 +148,7 @@ static void ttm_bo_reserve_deadlock(struct kunit *test) bo2 =ttm_bo_kunit_init (test, test->priv,BO_SIZE );ww_acquire_init (&ctx1, &reservation_ww_class); -mutex_lock (&bo2->base.resv->lock.base); +ww_mutex_base_lock (&bo2->base.resv->lock.base);/* The deadlock will be caught by WW mutex, don't warn about it */ lock_release (&bo2->base.resv->lock.base.dep_map,1 );
Signature · 1 line
2.43.0
Quoted 15 lines · On 2024-04-04 12:25:36 [+0200], To [email protected] wrote:
PREEMPT_RThas a different locking implementation forww_mutex. The base mutex of structww_mutexis declared as structWW_MUTEX_BASE. The latter is defined asmutex' for non-PREEMPT_RT builds andrt_mutex' forPREEMPT_RTbuilds.Using
mutex_lock()directly on the base mutex inttm_bo_reserve_deadlock()leads to compile error onPREEMPT_RT.The locking-selftest has its own defines to deal with this and it is probably best to defines the needed one within the test program since their usefulness is limited outside of well known selftests.
Provide
ww_mutex_base_lock()which points to the correct function forPREEMPT_RTand non-PREEMPT_RT builds.
Quoted 8 lines
Fixes 995279d280d1e ("drm/ttm/tests: Add tests for ttm_bo functions")Signed-off-by Sebastian Andrzej Siewior <[email protected]>---
For the record, testing led to
| WARNING: CPU: 5 PID: 2089 atinclude/drm/ttm/ttm_bo.h:247ttm_bo_reserve_no_wait_ticket+0xe8/0x150[ttm_bo_test]but this occurred with and without RT on v6.9-rc2.
a friendly ping.
Sebastian
Quoted 20 lines · On 2024-04-26 09:01:37 [+0200], To [email protected] wrote:
Quoted 19 lines · On 2024-04-04 12:25:36 [+0200], To [email protected] wrote:
PREEMPT_RThas a different locking implementation forww_mutex. The base mutex of structww_mutexis declared as structWW_MUTEX_BASE. The latter is defined asmutex' for non-PREEMPT_RT builds andrt_mutex' forPREEMPT_RTbuilds.Using
mutex_lock()directly on the base mutex inttm_bo_reserve_deadlock()leads to compile error onPREEMPT_RT.The locking-selftest has its own defines to deal with this and it is probably best to defines the needed one within the test program since their usefulness is limited outside of well known selftests.
Provide
ww_mutex_base_lock()which points to the correct function forPREEMPT_RTand non-PREEMPT_RT builds.Fixes 995279d280d1e ("drm/ttm/tests: Add tests for ttm_bo functions")Signed-off-by Sebastian Andrzej Siewior <[email protected]>---
Quoted 6 lines
Quoted 4 lines
For the record, testing led to
| WARNING: CPU: 5 PID: 2089 atinclude/drm/ttm/ttm_bo.h:247ttm_bo_reserve_no_wait_ticket+0xe8/0x150[ttm_bo_test]but this occurred with and without RT on v6.9-rc2.
a friendly ping.
ping ;)
Sebastian