From: Joel Fernandes <joelagnelf@nvidia.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
rcu <rcu@vger.kernel.org>, Joel Fernandes <joelagnelf@nvidia.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel-team <kernel-team@meta.com>, rostedt <rostedt@goodmis.org>
Subject: Re: [v2,04/12] rcutorture: Make torture.sh --do-rt use CONFIG_PREEMPT_RT
Date: Wed, 02 Apr 2025 12:19:13 -0400 [thread overview]
Message-ID: <5da8ff7a10670359647fc8135668be7c.joelagnelf@nvidia.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
Hello,
On Wed, 2 Apr 2025 16:17:06 GMT, Sebastian Andrzej Siewior wrote:
> 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.
Yeah, RCU_BOOST has default y if PREEMPT_RT.
Paul, should we be disabling it in the --do-rt script?
thanks,
- Joel
next reply other threads:[~2025-04-02 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 16:19 Joel Fernandes [this message]
2025-04-02 19:17 ` Paul E. McKenney
2025-04-05 11:01 ` Joel Fernandes
2025-04-05 17:10 ` Paul E. McKenney
2025-04-05 17:56 ` 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=5da8ff7a10670359647fc8135668be7c.joelagnelf@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=bigeasy@linutronix.de \
--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
all inboxes | Powered by JetHome®