From: Peter Zijlstra <peterz@infradead.org>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: rcu@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <quic_neeraju@quicinc.com>,
Joel Fernandes <joel@joelfernandes.org>,
Shuah Khan <shuah@kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, seanjc@google.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH rcu v2 0/7] RCU-related lockdep changes for v6.4
Date: Mon, 27 Mar 2023 17:14:58 +0200 [thread overview]
Message-ID: <20230327151458.GB11425@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230323042614.1191120-1-boqun.feng@gmail.com>
On Wed, Mar 22, 2023 at 09:26:07PM -0700, Boqun Feng wrote:
> Boqun Feng (4):
> locking/lockdep: Introduce lock_sync()
> rcu: Annotate SRCU's update-side lockdep dependencies
> locking: Reduce the number of locks in ww_mutex stress tests
> locking/lockdep: Improve the deadlock scenario print for sync and read
> lock
>
> Paul E. McKenney (3):
> rcutorture: Add SRCU deadlock scenarios
> rcutorture: Add RCU Tasks Trace and SRCU deadlock scenarios
> rcutorture: Add srcu_lockdep.sh
>
> include/linux/lockdep.h | 8 +-
> include/linux/srcu.h | 34 +++-
> kernel/locking/lockdep.c | 64 +++++-
> kernel/locking/test-ww_mutex.c | 2 +-
> kernel/rcu/rcutorture.c | 185 ++++++++++++++++++
> kernel/rcu/srcutiny.c | 2 +
> kernel/rcu/srcutree.c | 2 +
> .../selftests/rcutorture/bin/srcu_lockdep.sh | 78 ++++++++
> 8 files changed, 364 insertions(+), 11 deletions(-)
> create mode 100755 tools/testing/selftests/rcutorture/bin/srcu_lockdep.sh
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
prev parent reply other threads:[~2023-03-27 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 4:26 Boqun Feng
2023-03-23 4:26 ` [PATCH rcu v2 1/7] locking/lockdep: Introduce lock_sync() Boqun Feng
2023-03-23 4:26 ` [PATCH rcu v2 2/7] rcu: Annotate SRCU's update-side lockdep dependencies Boqun Feng
2023-03-23 4:26 ` [PATCH rcu v2 3/7] locking: Reduce the number of locks in ww_mutex stress tests Boqun Feng
2023-03-23 4:26 ` [PATCH rcu v2 4/7] locking/lockdep: Improve the deadlock scenario print for sync and read lock Boqun Feng
2023-03-23 4:26 ` [PATCH rcu v2 5/7] rcutorture: Add SRCU deadlock scenarios Boqun Feng
2023-03-23 4:26 ` [PATCH rcu v2 6/7] rcutorture: Add RCU Tasks Trace and " Boqun Feng
2023-03-23 4:26 ` [PATCH rcu v2 7/7] rcutorture: Add srcu_lockdep.sh Boqun Feng
2023-03-27 15:14 ` 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=20230327151458.GB11425@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=dave@stgolabs.net \
--cc=dwmw2@infradead.org \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=pbonzini@redhat.com \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--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
all inboxes | Powered by JetHome®