From: Joel Fernandes <jfern@kernel.org>
To: paulmck@kernel.org, rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Boqun Feng <boqun@kernel.org>, Joel Fernandes <jfern@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Uladzislau Rezki <urezki@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: [PATCH v2 0/7] rcutorture: Rewrite RCU priority-boost test around a CPU-hungry reader
Date: Mon, 16 Nov 2026 14:44:31 -0500 [thread overview]
Message-ID: <20261116194438.306618-1-jfern@kernel.org> (raw)
Hi,
This is v2 of the series that rewrites rcutorture's RCU priority-boost test
around a CPU-hungry reader, so that it neither depends on disabling RT
throttling nor infers boost failure from a grace period merely taking too
long. The approach is unchanged, see the v1 cover letter for the full
description:
v1: https://lore.kernel.org/all/20261111213826.2035045-1-joelagnelf@nvidia.com/
Changes since v1 (all from Sebastian's review, thanks!):
- 1/7: Use kthread_run_on_cpu() for the reader thread. Range-check
test_boost_reader_ms in rcu_torture_init(), clamping it to between
1 ms and test_boost_duration. Use div64_ul() when printing the
reader's CPU time.
- 2/7: Replaced by Sebastian's patch [1], which also removes the
sysctl_sched_rt_runtime declaration from rcu.h.
- 3/7: Drop the sched/sysctl.h include that crept in through a bad fold,
and also remove rcu_check_boost_fail(), which has no callers left.
- 4/7-7/7: Unchanged, other than the rebase.
- Rebased onto the current rcu/next.
Testing: kvm.sh with --duration 30 and --cpus set to all CPUs, on x86 (32
CPUs) and arm64 (80 Neoverse-N1 cores). Boost failures / boost intervals:
Scenario x86 arm64
TREE03 0 / 220 0 / 217
BUSTED-BOOST 247 / 252 250 / 251 (expected, boosting disabled)
[1] https://lore.kernel.org/all/20261113-sched_dl-v3-3-a76ffa1cdeee@linutronix.de/
Joel Fernandes (6):
rcutorture: Rewrite RCU priority-boost test around a CPU-hungry reader
rcutorture: Remove unused check_boost_failed hook
doc: Document rcutorture.test_boost_reader_ms
rcu: Add rcutree.boost_disable to disable priority boosting at runtime
doc: Document rcutree.boost_disable
rcutorture: Make BUSTED-BOOST disable RCU priority boosting
Sebastian Andrzej Siewior (1):
rcutorture: Don't try to disable to RT throttling.
.../admin-guide/kernel-parameters.txt | 14 ++
kernel/rcu/rcu.h | 4 -
kernel/rcu/rcutorture.c | 197 +++++++++---------
kernel/rcu/tree_plugin.h | 5 +-
kernel/rcu/tree_stall.h | 57 -----
.../rcutorture/configs/rcu/BUSTED-BOOST.boot | 1 +
6 files changed, 120 insertions(+), 158 deletions(-)
base-commit: e97b821f72876c4760bddc79f0858155e012da8b
--
2.54.0
next reply other threads:[~2026-11-16 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 19:44 Joel Fernandes [this message]
2026-11-16 19:44 ` [PATCH v2 1/7] rcutorture: Rewrite RCU priority-boost test around a CPU-hungry reader Joel Fernandes
2026-11-16 19:44 ` [PATCH v2 2/7] rcutorture: Don't try to disable to RT throttling Joel Fernandes
2026-11-16 19:44 ` [PATCH v2 3/7] rcutorture: Remove unused check_boost_failed hook Joel Fernandes
2026-11-16 19:44 ` [PATCH v2 4/7] doc: Document rcutorture.test_boost_reader_ms Joel Fernandes
2026-11-16 19:44 ` [PATCH v2 5/7] rcu: Add rcutree.boost_disable to disable priority boosting at runtime Joel Fernandes
2026-11-16 19:44 ` [PATCH v2 6/7] doc: Document rcutree.boost_disable Joel Fernandes
2026-11-16 19:44 ` [PATCH v2 7/7] rcutorture: Make BUSTED-BOOST disable RCU priority boosting Joel Fernandes
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=20261116194438.306618-1-jfern@kernel.org \
--to=jfern@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=boqun@kernel.org \
--cc=corbet@lwn.net \
--cc=dave@stgolabs.net \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=urezki@gmail.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 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.