From: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
To: "Paul E . McKenney" <paulmck@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>
Cc: 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>,
Uladzislau Rezki <urezki@gmail.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Subject: [PATCH 2/4] torture: Remove CONFIG_NR_CPUS configuration
Date: Thu, 23 Jan 2025 19:58:26 +0100 [thread overview]
Message-ID: <20250123185828.460836-2-urezki@gmail.com> (raw)
In-Reply-To: <20250123185828.460836-1-urezki@gmail.com>
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>
---
tools/testing/selftests/rcutorture/configs/rcu/TREE05 | 1 -
1 file changed, 1 deletion(-)
diff --git a/tools/testing/selftests/rcutorture/configs/rcu/TREE05 b/tools/testing/selftests/rcutorture/configs/rcu/TREE05
index 9f48c73709ec..d6fbb82e3e6d 100644
--- a/tools/testing/selftests/rcutorture/configs/rcu/TREE05
+++ b/tools/testing/selftests/rcutorture/configs/rcu/TREE05
@@ -1,5 +1,4 @@
CONFIG_SMP=y
-CONFIG_NR_CPUS=8
CONFIG_PREEMPT_NONE=y
CONFIG_PREEMPT_VOLUNTARY=n
CONFIG_PREEMPT=n
--
2.39.5
next prev parent reply other threads:[~2025-01-23 18:58 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 ` Uladzislau Rezki (Sony) [this message]
2025-01-23 20:29 ` [PATCH 2/4] torture: Remove CONFIG_NR_CPUS configuration 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
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=20250123185828.460836-2-urezki@gmail.com \
--to=urezki@gmail.com \
--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=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--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