[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <72693320-1863-4e47-941f-0e887f87a855@paulmck-laptop>
Date: Wed, 2 Apr 2025 12:17:34 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Joel Fernandes <joelagnelf@...dia.com>
Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
rcu <rcu@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
kernel-team <kernel-team@...a.com>, rostedt <rostedt@...dmis.org>
Subject: Re: [v2,04/12] rcutorture: Make torture.sh --do-rt use
CONFIG_PREEMPT_RT
On Wed, Apr 02, 2025 at 12:19:13PM -0400, Joel Fernandes wrote:
> 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?
You should have a "rcutorture.test_boost=0" from f2ac55968df2
("rcutorture: Make torture.sh --do-rt use CONFIG_PREEMPT_RT").
Plus I just now made additional adjustments based on Sebastian Siewior's
feedback. He is likely to have additional feedback, so this is currently
a "squash!" commit in my tree.
Thanx, Paul
Powered by blists - more mailing lists