As part of the proxy-exec work, I've leveraged the ww_mutex test
driver to help stress test the lock handling.

Two of these patches I've sent a few times without any
response[1], but after realizing the test wasn't exercising the
wait-wound class mutexes (only wait-die), I've extended the test
driver to now do both. This helps make sure there is more
confidence in any changes being made.

I've reworked my older changes ontop of that and wanted to send
them all out for consideration.

Any feedback would be greatly appreciated.

Thanks!
-john

Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Will Deacon <will@kernel.org>
Cc: Waiman Long <longman@redhat.com>
Cc: Boqun Feng <boqun.feng@gmail.com>
Cc: "Paul E . McKenney" <paulmck@kernel.org>
Cc: Joel Fernandes <joelagnelf@nvidia.com>
Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: Suleiman Souhlal <suleiman@google.com>
Cc: kernel-team@android.com

John Stultz (3):
  test-ww_mutex: Extend ww_mutex tests to test both classes of
    ww_mutexes
  test-ww_mutex: Move work to its own UNBOUND workqueue
  test-ww_mutex: Allow test to be run (and re-run) from userland

 kernel/locking/test-ww_mutex.c | 165 ++++++++++++++++++++++++---------
 1 file changed, 122 insertions(+), 43 deletions(-)

-- 
2.50.1.565.gc32cd1483b-goog

On Thu, Jul 31, 2025 at 7:34 PM John Stultz <jstultz@google.com> wrote:
>
> As part of the proxy-exec work, I've leveraged the ww_mutex test
> driver to help stress test the lock handling.
>
> Two of these patches I've sent a few times without any
> response[1], but after realizing the test wasn't exercising the
> wait-wound class mutexes (only wait-die), I've extended the test
> driver to now do both. This helps make sure there is more
> confidence in any changes being made.

Forgot to add the link I intended:
[1]: https://lore.kernel.org/lkml/20250715021417.4015799-1-jstultz@google.com/

thanks
-john