From: "Paul E. McKenney" <paulmck@kernel.org>
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
rostedt@goodmis.org, "Paul E. McKenney" <paulmck@kernel.org>
Subject: [PATCH 1/9] doc: Update stallwarn.rst based on RCU Tasks Trace as SRCU
Date: Fri, 18 Sep 2026 17:28:52 -0700 [thread overview]
Message-ID: <20260919002900.3134117-1-paulmck@kernel.org> (raw)
In-Reply-To: <7dc2d858-44cc-4efa-8e94-1fe27d691f2b@paulmck-laptop>
Now that RCU Tasks Trace has been re-implemented in terms of SRCU,
update stallwarn.rst to remove obsolete verbiage about RCU Tasks Trace
stall warnings.
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
---
Documentation/RCU/stallwarn.rst | 22 +++++++++-------------
1 file changed, 9 insertions(+), 13 deletions(-)
diff --git a/Documentation/RCU/stallwarn.rst b/Documentation/RCU/stallwarn.rst
index d7c8eff63317..a986358a5c27 100644
--- a/Documentation/RCU/stallwarn.rst
+++ b/Documentation/RCU/stallwarn.rst
@@ -122,10 +122,11 @@ warnings:
of RCU CPU stall warnings, eventually leading to the realization
that the CPU had failed.
-The RCU, RCU-sched, RCU-tasks, and RCU-tasks-trace implementations have
-CPU stall warning. Note that SRCU does *not* have CPU stall warnings.
-Please note that RCU only detects CPU stalls when there is a grace period
-in progress. No grace period, no CPU stall warnings.
+The RCU and RCU-tasks implementations have CPU stall warning. Note that
+SRCU does *not* have CPU stall warnings, and now that RCU-tasks-trace
+is implemented in terms of SRCU, neither does it. Please note that
+RCU only detects CPU stalls when there is a grace period in progress.
+No grace period, no CPU stall warnings.
To diagnose the cause of the stall, inspect the stack traces.
The offending function will usually be near the top of the stack.
@@ -213,21 +214,16 @@ RCU_STALL_RAT_DELAY
rcupdate.rcu_task_stall_timeout
-------------------------------
- This boot/sysfs parameter controls the RCU-tasks and
- RCU-tasks-trace stall warning intervals. A value of zero or less
- suppresses RCU-tasks stall warnings. A positive value sets the
- stall-warning interval in seconds. An RCU-tasks stall warning
- starts with the line:
+ This boot/sysfs parameter controls the RCU-tasks stall warning
+ interval. A value of zero or less suppresses RCU-tasks stall
+ warnings. A positive value sets the stall-warning interval
+ in seconds. An RCU-tasks stall warning starts with the line:
INFO: rcu_tasks detected stalls on tasks:
And continues with the output of sched_show_task() for each
task stalling the current RCU-tasks grace period.
- An RCU-tasks-trace stall warning starts (and continues) similarly:
-
- INFO: rcu_tasks_trace detected stalls on tasks
-
Interpreting RCU's CPU Stall-Detector "Splats"
==============================================
--
2.40.1
next prev parent reply other threads:[~2026-09-19 0:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 0:28 [PATCH 0/9] Miscellaneous RCU updates for v7.4 Paul E. McKenney
2026-09-19 0:28 ` Paul E. McKenney [this message]
2026-09-19 0:28 ` [PATCH 2/9] rcu: fix shrink budget underflow in lazy_rcu_shrink_scan Paul E. McKenney
2026-09-19 0:28 ` [PATCH 3/9] rcu: Don't panic on already-ended RCU CPU stalls Paul E. McKenney
2026-09-19 0:28 ` [PATCH 4/9] rcu: Add running and boosted indications to RCU task stall dump Paul E. McKenney
2026-09-19 0:28 ` [PATCH 5/9] rcu: Fix typo "upto" in comment Paul E. McKenney
2026-09-19 0:28 ` [PATCH 6/9] rcu: Drop the private tick-internal.h include from tree.c Paul E. McKenney
2026-09-19 0:28 ` [PATCH 7/9] rcu: Make userspace barrier hook drain kvfree_rcu work Paul E. McKenney
2026-09-19 0:28 ` [PATCH 8/9] rcuref: Fix the rcuread_is_dead reference in rcuref_read() kernel-doc Paul E. McKenney
2026-09-19 0:29 ` [PATCH 9/9] rcu-tasks: Disable callback contend/collapse messages by default 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=20260919002900.3134117-1-paulmck@kernel.org \
--to=paulmck@kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.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 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®