From: Boqun Feng <boqun.feng@gmail.com>
To: rcu@vger.kernel.org
Cc: Davidlohr Bueso <dave@stgolabs.net>,
"Paul E. McKenney" <paulmck@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <quic_neeraju@quicinc.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
Shuah Khan <shuah@kernel.org>,
Bhaskar Chowdhury <unixbhaskar@gmail.com>,
Boqun Feng <boqun.feng@gmail.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
"Zhang, Qiang1" <qiang1.zhang@intel.com>
Subject: [PATCH rcu v2 02/10] rcutorture: Set CONFIG_BOOTPARAM_HOTPLUG_CPU0 to offline CPU 0
Date: Wed, 22 Mar 2023 21:39:27 -0700 [thread overview]
Message-ID: <20230323043935.1221184-3-boqun.feng@gmail.com> (raw)
In-Reply-To: <20230323043935.1221184-1-boqun.feng@gmail.com>
From: "Paul E. McKenney" <paulmck@kernel.org>
There is now a BOOTPARAM_HOTPLUG_CPU0 Kconfig option that allows CPU 0
to be offlined on x86 systems. This commit therefore sets this option in
the TREE01 rcutorture scenario in order to regularly test this capability.
Reported-by: "Zhang, Qiang1" <qiang1.zhang@intel.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
---
tools/testing/selftests/rcutorture/configs/rcu/TREE01 | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/rcutorture/configs/rcu/TREE01 b/tools/testing/selftests/rcutorture/configs/rcu/TREE01
index 8ae41d5f81a3..04831ef1f9b5 100644
--- a/tools/testing/selftests/rcutorture/configs/rcu/TREE01
+++ b/tools/testing/selftests/rcutorture/configs/rcu/TREE01
@@ -15,3 +15,4 @@ CONFIG_DEBUG_LOCK_ALLOC=n
CONFIG_RCU_BOOST=n
CONFIG_DEBUG_OBJECTS_RCU_HEAD=n
CONFIG_RCU_EXPERT=y
+CONFIG_BOOTPARAM_HOTPLUG_CPU0=y
--
2.38.1
next prev parent reply other threads:[~2023-03-23 4:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 4:39 [PATCH rcu v2 00/10] RCU torture test and tool updates for v6.4 Boqun Feng
2023-03-23 4:39 ` [PATCH rcu v2 01/10] rcutorture: Add test_nmis module parameter Boqun Feng
2023-03-23 4:39 ` Boqun Feng [this message]
2023-03-23 4:39 ` [PATCH rcu v2 03/10] rcutorture: Make scenario TREE04 enable lazy call_rcu() Boqun Feng
2023-03-23 4:39 ` [PATCH rcu v2 04/10] tools: rcu: Add usage function and check for argument Boqun Feng
2023-03-23 4:39 ` [PATCH rcu v2 05/10] torture: Permit kvm-again.sh --duration to default to previous run Boqun Feng
2023-03-23 4:39 ` [PATCH rcu v2 06/10] rcutorture: Eliminate variable n_rcu_torture_boost_rterror Boqun Feng
2023-03-23 4:39 ` [PATCH rcu v2 07/10] torture: Enable clocksource watchdog with "tsc=watchdog" Boqun Feng
2023-03-23 4:39 ` [PATCH rcu v2 08/10] rcutorture: Create nocb kthreads only when testing rcu in CONFIG_RCU_NOCB_CPU=y kernels Boqun Feng
2023-03-23 4:39 ` [PATCH rcu v2 09/10] rcuscale: Move shutdown from wait_event() to wait_event_idle() Boqun Feng
2023-03-23 4:39 ` [PATCH rcu v2 10/10] refscale: " Boqun Feng
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=20230323043935.1221184-3-boqun.feng@gmail.com \
--to=boqun.feng@gmail.com \
--cc=dave@stgolabs.net \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=qiang1.zhang@intel.com \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=unixbhaskar@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;
as well as URLs for NNTP newsgroup(s).