From: "Joel Fernandes (Google)" <joel@joelfernandes.org>
To: linux-kernel@vger.kernel.org
Cc: "Joel Fernandes (Google)" <joel@joelfernandes.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Josh Triplett <josh@joshtriplett.org>,
kernel-team@android.com, Lai Jiangshan <jiangshanlai@gmail.com>,
linux-doc@vger.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
rcu@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>
Subject: [RFC v1 0/2] RCU dyntick nesting counter cleanups
Date: Mon, 26 Aug 2019 21:33:52 -0400 [thread overview]
Message-ID: <5d648893.1c69fb81.5e60a.fc6c@mx.google.com> (raw)
These patches clean up the usage of dynticks nesting counters simplifying the
code, while preserving the usecases.
It is a much needed simplification, makes the code less confusing, and prevents
future bugs such as those that arise from forgetting that the
dynticks_nmi_nesting counter is not a simple counter and can be "crowbarred" in
common situations.
Several nights of rcutorture testing with CONFIG_RCU_EQS_DEBUG on all RCU
kernel configurations have survived without any splats.
Further testing is in progress, hence marked as RFC!
thanks,
- Joel
Joel Fernandes (Google) (2):
rcu/tree: Clean up dynticks counter usage
rcu/tree: Remove dynticks_nmi_nesting counter
.../Data-Structures/Data-Structures.rst | 31 ++----
Documentation/RCU/stallwarn.txt | 6 +-
kernel/rcu/rcu.h | 4 -
kernel/rcu/tree.c | 98 +++++++++----------
kernel/rcu/tree.h | 4 +-
kernel/rcu/tree_stall.h | 4 +-
6 files changed, 64 insertions(+), 83 deletions(-)
--
2.23.0.187.g17f5b7556c-goog
next reply other threads:[~2019-08-27 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 1:33 Joel Fernandes (Google) [this message]
2019-08-28 0:11 ` [RFC v1 0/2] RCU dyntick nesting counter cleanups Paul E. McKenney
2019-08-28 18:26 ` [PATCH] rcu/dyntick-idle: Add better tracing Joel Fernandes (Google)
2019-08-28 23:05 ` Paul E. McKenney
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=5d648893.1c69fb81.5e60a.fc6c@mx.google.com \
--to=joel@joelfernandes.org \
--cc=corbet@lwn.net \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=kernel-team@android.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mchehab+samsung@kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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.