From: Davidlohr Bueso <dave@stgolabs.net>
To: John Stultz <jstultz@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Joel Fernandes <joel@joelfernandes.org>,
Juri Lelli <juri.lelli@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>
Subject: Re: [PATCH v2 3/4] locktorture: Add nested locking to rtmutex torture tests
Date: Sun, 5 Feb 2023 11:00:34 -0800 [thread overview]
Message-ID: <20230205190034.hlvisuduu7sdrrv4@offworld> (raw)
In-Reply-To: <20230203200138.3872873-3-jstultz@google.com>
On Fri, 03 Feb 2023, John Stultz wrote:
>This patch adds randomized nested locking to the rtmutex torture
>tests. Additionally it adds LOCK09 config files for testing
>rtmutexes with nested locking.
>
>This was inspired by locktorture extensions originally implemented
>by Connor O'Brien, for stress testing the proxy-execution series:
> https://lore.kernel.org/lkml/20221003214501.2050087-12-connoro@google.com/
>
>Comments or feedback would be greatly appreciated!
>
>Cc: Davidlohr Bueso <dave@stgolabs.net>
>Cc: "Paul E. McKenney" <paulmck@kernel.org>
>Cc: Josh Triplett <josh@joshtriplett.org>
>Cc: Joel Fernandes <joel@joelfernandes.org>
>Cc: Juri Lelli <juri.lelli@redhat.com>
>Cc: Valentin Schneider <vschneid@redhat.com>
>Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>
>Signed-off-by: John Stultz <jstultz@google.com>
Reviewed-by: Davidlohr Bueso <dave@stgolabs.net>
next prev parent reply other threads:[~2023-02-05 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 20:01 [PATCH v2 1/4] locktorture: Add nested_[un]lock() hooks and nlocks parameter John Stultz
2023-02-03 20:01 ` [PATCH v2 2/4] locktorture: Add nested locking to mutex torture tests John Stultz
2023-02-05 19:07 ` Davidlohr Bueso
2023-02-06 17:20 ` Paul E. McKenney
2023-02-06 19:24 ` John Stultz
2023-02-03 20:01 ` [PATCH v2 3/4] locktorture: Add nested locking to rtmutex " John Stultz
2023-02-05 18:58 ` Davidlohr Bueso
2023-02-05 19:00 ` Davidlohr Bueso [this message]
2023-02-03 20:01 ` [PATCH v2 4/4] locktorture: With nested locks, occasionally skip main lock John Stultz
2023-02-05 19:05 ` Davidlohr Bueso
2023-02-06 20:37 ` John Stultz
2023-02-03 23:38 ` [PATCH v2 1/4] locktorture: Add nested_[un]lock() hooks and nlocks parameter Paul E. McKenney
2023-02-05 18:34 ` Davidlohr Bueso
2023-02-06 19:44 ` 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=20230205190034.hlvisuduu7sdrrv4@offworld \
--to=dave@stgolabs.net \
--cc=dietmar.eggemann@arm.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=vschneid@redhat.com \
/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
all inboxes | Powered by JetHome®