From: Peter Zijlstra <peterz@infradead.org>
To: John Stultz <jstultz@google.com>
Cc: LKML <linux-kernel@vger.kernel.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: Re: [RESEND x5][PATCH 0/3] test-ww_mutex improvements
Date: Fri, 5 Dec 2025 16:25:12 +0100 [thread overview]
Message-ID: <20251205152512.GD2528459@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20251205013515.759030-1-jstultz@google.com>
On Fri, Dec 05, 2025 at 01:35:08AM +0000, John Stultz wrote:
> Hey all,
> Felt like yelling into the void again to resend my improvements
> to the test-ww_mutex test driver. These changes have been
> particularly helpful for tripping issues in the proxy-exec series.
Right you are. I've thrown these on the pile to sort out post rc1.
prev parent reply other threads:[~2025-12-05 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 1:35 [RESEND x5][PATCH 0/3] test-ww_mutex improvements John Stultz
2025-12-05 1:35 ` [RESEND x5][PATCH 1/3] test-ww_mutex: Extend ww_mutex tests to test both classes of ww_mutexes John Stultz
2025-12-18 9:51 ` [tip: locking/core] " tip-bot2 for John Stultz
2025-12-05 1:35 ` [RESEND x5][PATCH 2/3] test-ww_mutex: Move work to its own UNBOUND workqueue John Stultz
2025-12-18 9:51 ` [tip: locking/core] " tip-bot2 for John Stultz
2025-12-05 1:35 ` [RESEND x5][PATCH 3/3] test-ww_mutex: Allow test to be run (and re-run) from userland John Stultz
2025-12-18 9:51 ` [tip: locking/core] " tip-bot2 for John Stultz
2025-12-05 15:25 ` Peter Zijlstra [this message]
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=20251205152512.GD2528459@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelagnelf@nvidia.com \
--cc=jstultz@google.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox