Commit d327e716 authored by John Stultz's avatar John Stultz Committed by Peter Zijlstra
Browse files

test-ww_mutex: Move work to its own UNBOUND workqueue 



The test-ww_mutex test already allocates its own workqueue
so be sure to use it for the mtx.work and abba.work rather
then the default system workqueue.

This resolves numerous messages of the sort:
"workqueue: test_abba_work hogged CPU... consider switching to WQ_UNBOUND"
"workqueue: test_mutex_work hogged CPU... consider switching to WQ_UNBOUND"

Signed-off-by: default avatarJohn Stultz <jstultz@google.com>
Signed-off-by: default avatarPeter Zijlstra (Intel) <peterz@infradead.org>
Link: https://patch.msgid.link/20251205013515.759030-3-jstultz@google.com
parent 34d80c93

kernel/locking/test-ww_mutex.c

+2 −2
Original line number Diff line number Diff line
@@ -72,7 +72,7 @@ static int __test_mutex(struct ww_class *class, unsigned int flags) 
	init_completion(&mtx.done);

	mtx.flags = flags;



	schedule_work(&mtx.work);

	queue_work(wq, &mtx.work);



	wait_for_completion(&mtx.ready);

	ww_mutex_lock(&mtx.mutex, (flags & TEST_MTX_CTX) ? &ctx : NULL);
@@ -234,7 +234,7 @@ static int test_abba(struct ww_class *class, bool trylock, bool resolve) 
	abba.trylock = trylock;

	abba.resolve = resolve;



	schedule_work(&abba.work);

	queue_work(wq, &abba.work);



	ww_acquire_init_noinject(&ctx, class);

	if (!trylock)