From: John Stultz <jstultz@google.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: John Stultz <jstultz@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
"Paul E . McKenney" <paulmck@kernel.org>,
Joel Fernandes <joelagnelf@nvidia.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Suleiman Souhlal <suleiman@google.com>,
kernel-team@android.com
Subject: [PATCH 0/3] Improvements to ww_mutex test driver
Date: Fri, 1 Aug 2025 02:33:46 +0000 [thread overview]
Message-ID: <20250801023358.562525-1-jstultz@google.com> (raw)
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
next reply other threads:[~2025-08-01 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 2:33 John Stultz [this message]
2025-08-01 2:33 ` [PATCH 1/3] test-ww_mutex: Extend ww_mutex tests to test both classes of ww_mutexes John Stultz
2025-08-01 2:33 ` [PATCH 2/3] test-ww_mutex: Move work to its own UNBOUND workqueue John Stultz
2025-08-01 2:33 ` [PATCH 3/3] test-ww_mutex: Allow test to be run (and re-run) from userland John Stultz
2025-08-01 2:46 ` [PATCH 0/3] Improvements to ww_mutex test driver John Stultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250801023358.562525-1-jstultz@google.com \
--to=jstultz@google.com \
--cc=boqun.feng@gmail.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelagnelf@nvidia.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=suleiman@google.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.