public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: [RESEND x5][PATCH 0/3] test-ww_mutex improvements
Date: Fri,  5 Dec 2025 01:35:08 +0000	[thread overview]
Message-ID: <20251205013515.759030-1-jstultz@google.com> (raw)

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.

Despite sending these a few times, I've not gotten any response.
I get its sort of a minor test driver, and isn't super urgent,
but it would be nice to move these forward upstream instead of
having them carried in one of my branches and having to remember
to pull them in when I test with vanilla upstream trees.

As always feedback would be appreciated. Do let me know if I 
hould be cc'ing someone I'm missing to get these reviewed and
eventually pulled in.

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.52.0.223.gf5cc29aaa4-goog


             reply	other threads:[~2025-12-05  1:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05  1:35 John Stultz [this message]
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 ` [RESEND x5][PATCH 0/3] test-ww_mutex improvements Peter Zijlstra

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=20251205013515.759030-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox