From: "Paul E. McKenney" <paulmck@kernel.org>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: Boqun Feng <boqun.feng@gmail.com>, RCU <rcu@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Cheung Wall <zzqq0103.hey@gmail.com>,
Neeraj upadhyay <Neeraj.Upadhyay@amd.com>,
Joel Fernandes <joel@joelfernandes.org>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Subject: Re: [PATCH 2/4] torture: Remove CONFIG_NR_CPUS configuration
Date: Fri, 24 Jan 2025 09:36:07 -0800 [thread overview]
Message-ID: <c57daf05-1018-40b5-9684-22dfd94cc8d9@paulmck-laptop> (raw)
In-Reply-To: <Z5PMGlDb489VEZ7S@pc636>
On Fri, Jan 24, 2025 at 06:21:30PM +0100, Uladzislau Rezki wrote:
> On Fri, Jan 24, 2025 at 07:45:23AM -0800, Paul E. McKenney wrote:
> > On Fri, Jan 24, 2025 at 12:41:38PM +0100, Uladzislau Rezki wrote:
> > > On Thu, Jan 23, 2025 at 12:29:45PM -0800, Paul E. McKenney wrote:
> > > > On Thu, Jan 23, 2025 at 07:58:26PM +0100, Uladzislau Rezki (Sony) wrote:
> > > > > This configuration specifies the maximum number of CPUs which
> > > > > is set to 8. The problem is that it can not be overwritten for
> > > > > something higher.
> > > > >
> > > > > Remove that configuration for TREE05, so it is possible to run
> > > > > the torture test on as many CPUs as many system has.
> > > > >
> > > > > Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
> > > >
> > > > You should be able to override this on the kvm.sh command line by
> > > > specifying "--kconfig CONFIG_NR_CPUS=128" or whatever number you wish.
> > > > For example, see the torture.sh querying the system's number of CPUs
> > > > and then specifying it to a number of tests.
> > > >
> > > > Or am I missing something here?
> > > >
> > > It took me a while to understand what happens. Apparently there is this
> > > 8 CPUs limitation. Yes, i can do it manually by passing --kconfig but
> > > you need to know about that. I have not expected that.
> > >
> > > Therefore i removed it from the configuration because i have not found
> > > a good explanation why we need. It is confusing instead :)
> >
> > Right now, if I do a run with --configs "TREE10 14*CFLIST", this will
> > make use of 20 systems with 80 CPUs each. If you remove that line from
> > TREE05, won't each instance of TREE05 consume a full system, for a total
> > of 33 systems? Yes, I could use "--kconfig CONFIG_NR_CPUS=8" on the
> > command line, but that would affect all the scenarios, not just TREE05.
> > Including (say) TINY01, where I believe that it would cause kvm.sh
> > to complain about a Kconfig conflict.
> >
> > Hence me not being in favor of this change. ;-)
> >
> > Is there another way to make things work for both situations?
> >
> OK, i see. Well. I will just go with --kconfig CONFIG_NR_CPUS=foo if i
> need more CPUs for TREE05.
>
> I will not resist, we just drop this patch :)
Thank you!
The bug you are chasing happens when a given synchonize_rcu() interacts
with RCU readers, correct?
In rcutorture, only the rcu_torture_writer() call to synchronize_rcu()
interacts with rcu_torture_reader(). So my guess is that running
many small TREE05 guest OSes would reproduce this bug more quickly.
So instead of this:
--kconfig CONFIG_NR_CPUS=128
Do this:
--configs "16*TREE05"
Or maybe even this:
--configs "16*TREE05" --kconfig CONFIG_NR_CPUS=4
Thoughts?
Thanx, Paul
next prev parent reply other threads:[~2025-01-24 17:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 18:58 [PATCH 1/4] rcutorture: Allow a negative value for nfakewriters Uladzislau Rezki (Sony)
2025-01-23 18:58 ` [PATCH 2/4] torture: Remove CONFIG_NR_CPUS configuration Uladzislau Rezki (Sony)
2025-01-23 20:29 ` Paul E. McKenney
2025-01-24 11:41 ` Uladzislau Rezki
2025-01-24 15:45 ` Paul E. McKenney
2025-01-24 17:21 ` Uladzislau Rezki
2025-01-24 17:36 ` Paul E. McKenney [this message]
2025-01-24 17:48 ` Uladzislau Rezki
2025-01-24 19:34 ` Paul E. McKenney
2025-01-27 13:27 ` Uladzislau Rezki
2025-01-27 14:51 ` Paul E. McKenney
2025-01-27 15:42 ` Uladzislau Rezki
2025-01-27 16:51 ` Paul E. McKenney
2025-01-27 17:26 ` Uladzislau Rezki
2025-01-27 18:15 ` Paul E. McKenney
2025-01-27 18:31 ` Uladzislau Rezki
2025-01-27 19:24 ` Uladzislau Rezki
2025-01-27 20:37 ` Uladzislau Rezki
2025-01-28 0:14 ` Paul E. McKenney
2025-01-28 12:17 ` Uladzislau Rezki
2025-01-28 12:41 ` Paul E. McKenney
2025-01-28 14:34 ` Uladzislau Rezki
2025-01-28 18:43 ` Paul E. McKenney
2025-01-28 20:57 ` Uladzislau Rezki
2025-01-23 18:58 ` [PATCH 3/4] rcu: Update TREE05.boot to test normal synchronize_rcu() Uladzislau Rezki (Sony)
2025-01-23 20:30 ` Paul E. McKenney
2025-01-23 18:58 ` [PATCH 4/4] rcu: Use _full() API to debug synchronize_rcu() Uladzislau Rezki (Sony)
2025-01-23 21:52 ` Paul E. McKenney
2025-01-24 11:48 ` Uladzislau Rezki
2025-01-24 15:49 ` Paul E. McKenney
2025-01-28 20:55 ` [PATCH 1/4] rcutorture: Allow a negative value for nfakewriters Uladzislau Rezki
2025-01-28 21:19 ` 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=c57daf05-1018-40b5-9684-22dfd94cc8d9@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=Neeraj.Upadhyay@amd.com \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksiy.avramchenko@sony.com \
--cc=rcu@vger.kernel.org \
--cc=urezki@gmail.com \
--cc=zzqq0103.hey@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 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®