From: "Paul E. McKenney" <paulmck@kernel.org>
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com,
mingo@kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
fweisbec@gmail.com, oleg@redhat.com, joel@joelfernandes.org
Subject: [PATCH tip/core/rcu 0/3] RCU stall-warning updates for v5.8
Date: Wed, 15 Apr 2020 10:23:41 -0700 [thread overview]
Message-ID: <20200415172341.GA9519@paulmck-ThinkPad-P72> (raw)
Hello!
This series provides a few updates to RCU CPU stall-warning messages.
1. Use data_race() for RCU expedited CPU stall-warning prints.
2. When GP kthread is starved, tag idle threads as false positives.
After all, it is not the idle threads' fault that the GP
kthread hasn't reported their extended quiescent states!
3. Remove self-stack-trace when all quiescent states seen.
Thanx, Paul
------------------------------------------------------------------------
tree_exp.h | 8 ++++----
tree_stall.h | 26 +++++++++++++++++++-------
2 files changed, 23 insertions(+), 11 deletions(-)
next reply other threads:[~2020-04-15 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 17:23 Paul E. McKenney [this message]
2020-04-15 17:24 ` [PATCH tip/core/rcu 1/3] rcu: Use data_race() for RCU expedited CPU stall-warning prints paulmck
2020-04-15 17:24 ` [PATCH tip/core/rcu 2/3] rcu: When GP kthread is starved, tag idle threads as false positives paulmck
2020-04-15 17:24 ` [PATCH tip/core/rcu 3/3] rcu: Remove self-stack-trace when all quiescent states seen paulmck
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=20200415172341.GA9519@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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