From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: rcu@vger.kernel.org, Joel Fernandes <joelagnelf@nvidia.com>,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
rostedt@goodmis.org
Subject: Re: [PATCH v2 04/12] rcutorture: Make torture.sh --do-rt use CONFIG_PREEMPT_RT
Date: Wed, 2 Apr 2025 09:42:11 +0200 [thread overview]
Message-ID: <20250402074211.tibxg1fJ@linutronix.de> (raw)
In-Reply-To: <20250331210314.590622-4-paulmck@kernel.org>
On 2025-03-31 14:03:06 [-0700], Paul E. McKenney wrote:
> The torture.sh --do-rt command-line parameter is intended to mimic -rt
> kernels. Now that CONFIG_PREEMPT_RT is upstream, this commit makes this
> mimicking more precise.
>
> Note that testing of RCU priority boosting is disabled in favor
> of forward-progress testing of RCU callbacks. If it turns out to be
> possible to make kernels built with CONFIG_PREEMPT_RT=y to tolerate
> testing of both, both will be enabled.
Not sure what you point at here: You can build a PREEMPT_RT kernel and
RCU boosting is enabled by default. You could disable it if needed.
Config wise you set CONFIG_PREEMPT_LAZY=n but in general
CONFIG_PREEMPT_LAZY=y should be used if possible. The preemption while
holding a sleeping spinlock is somehow bad for performance if a lot of
threads ask for it. But then it probably doesn't matter for testing.
You do set rcupdate.rcu_normal and rcupdate.rcu_expedited but RT has
rcu_normal_after_boot set by default. Not sure if this makes any
difference but I *think* that normal wins here.
> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
> Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Sebastian
next prev parent reply other threads:[~2025-04-02 7:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 21:02 [PATCH v2 0/12] Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 01/12] rcutorture: Make srcu_lockdep.sh check kernel Kconfig Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 02/12] rcutorture: Make srcu_lockdep.sh check reader-conflict handling Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 03/12] rcutorture: Split out beginning and end from rcu_torture_one_read() Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 04/12] rcutorture: Make torture.sh --do-rt use CONFIG_PREEMPT_RT Paul E. McKenney
2025-04-02 7:42 ` Sebastian Andrzej Siewior [this message]
2025-04-02 18:51 ` Paul E. McKenney
2025-04-07 19:12 ` [PATCH v3 4/12] " Paul E. McKenney
2025-04-08 14:29 ` [v3,4/12] " Joel Fernandes
2025-04-08 16:20 ` Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 05/12] rcutorture: Add tests for SRCU up/down reader primitives Paul E. McKenney
2025-04-08 20:18 ` [v2,05/12] " Joel Fernandes
2025-04-08 20:58 ` Paul E. McKenney
2025-04-08 22:05 ` Joel Fernandes
2025-04-08 22:21 ` Paul E. McKenney
2025-04-15 17:16 ` [PATCH v2 05/12] " Joel Fernandes
2025-04-15 17:59 ` Paul E. McKenney
2025-04-15 21:15 ` Paul E. McKenney
2025-04-16 1:14 ` Joel Fernandes
2025-04-16 3:55 ` Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 06/12] rcutorture: Pull rcu_torture_updown() loop body into new function Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 07/12] rcutorture: Comment invocations of tick_dep_set_task() Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 08/12] rcutorture: Complain if an ->up_read() is delayed more than 10 seconds Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 09/12] rcutorture: Check for ->up_read() without matching ->down_read() Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 10/12] checkpatch: Deprecate srcu_read_lock_lite() and srcu_read_unlock_lite() Paul E. McKenney
2025-04-01 6:53 ` Joe Perches
2025-04-01 14:05 ` Paul E. McKenney
2025-04-02 3:48 ` Joe Perches
2025-04-02 4:23 ` Paul E. McKenney
2025-04-02 4:49 ` Joe Perches
2025-04-02 14:12 ` Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 11/12] torture: Add --do-{,no-}normal to torture.sh Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 12/12] torture: Add testing of RCU's Rust bindings " Paul E. McKenney
2025-04-02 14:45 ` [PATCH v2 0/12] 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=20250402074211.tibxg1fJ@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=joelagnelf@nvidia.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox