From: "Paul E. McKenney" <paulmck@kernel.org>
To: Joel Fernandes <joelagnelf@nvidia.com>
Cc: Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC v1 4/4] rcutorture: Add NOCB02 config for nocb poll mode testing
Date: Wed, 25 Feb 2026 13:47:24 -0800 [thread overview]
Message-ID: <89367e04-7647-4165-be41-385b61aa131b@paulmck-laptop> (raw)
In-Reply-To: <20260224230435.3390963-5-joelagnelf@nvidia.com>
On Tue, Feb 24, 2026 at 06:04:35PM -0500, Joel Fernandes wrote:
> Add new rcutorture config NOCB02 that enables rcu_nocb_poll boot
> parameter combined with CONFIG_RCU_NOCB_CPU to exercise the polling
> mode code paths in the NOCB implementation.
>
> This config exercises poll-mode paths not covered by other configs,
> where callback invocation uses active polling instead of kthread
> wakeups.
>
> This config is not added to CFLIST to avoid increasing the default
> test duration; it can be run explicitly when poll-mode testing
> is needed.
>
> Signed-off-by: Joel Fernandes <joelagnelf@nvidia.com>
For 3/4 and 4/4:
Reviewed-by: Paul E. McKenney <paulmck@kernel.org>
Tested-by: Paul E. McKenney <paulmck@kernel.org>
> ---
> .../selftests/rcutorture/configs/rcu/NOCB02 | 20 +++++++++++++++++++
> .../rcutorture/configs/rcu/NOCB02.boot | 3 +++
> 2 files changed, 23 insertions(+)
> create mode 100644 tools/testing/selftests/rcutorture/configs/rcu/NOCB02
> create mode 100644 tools/testing/selftests/rcutorture/configs/rcu/NOCB02.boot
>
> diff --git a/tools/testing/selftests/rcutorture/configs/rcu/NOCB02 b/tools/testing/selftests/rcutorture/configs/rcu/NOCB02
> new file mode 100644
> index 000000000000..4c2b8cd6d8fd
> --- /dev/null
> +++ b/tools/testing/selftests/rcutorture/configs/rcu/NOCB02
> @@ -0,0 +1,20 @@
> +CONFIG_SMP=y
> +CONFIG_NR_CPUS=8
> +CONFIG_PREEMPT_NONE=n
> +CONFIG_PREEMPT_VOLUNTARY=n
> +CONFIG_PREEMPT=y
> +#CHECK#CONFIG_PREEMPT_RCU=y
> +CONFIG_HZ_PERIODIC=n
> +CONFIG_NO_HZ_IDLE=y
> +CONFIG_NO_HZ_FULL=n
> +CONFIG_RCU_TRACE=y
> +CONFIG_HOTPLUG_CPU=y
> +CONFIG_RCU_FANOUT=3
> +CONFIG_RCU_FANOUT_LEAF=2
> +CONFIG_RCU_NOCB_CPU=y
> +CONFIG_DEBUG_LOCK_ALLOC=n
> +CONFIG_PROVE_LOCKING=n
> +CONFIG_RCU_BOOST=n
> +CONFIG_DEBUG_OBJECTS_RCU_HEAD=n
> +CONFIG_RCU_EXPERT=y
> +CONFIG_RCU_EQS_DEBUG=y
> diff --git a/tools/testing/selftests/rcutorture/configs/rcu/NOCB02.boot b/tools/testing/selftests/rcutorture/configs/rcu/NOCB02.boot
> new file mode 100644
> index 000000000000..c212ae299b0b
> --- /dev/null
> +++ b/tools/testing/selftests/rcutorture/configs/rcu/NOCB02.boot
> @@ -0,0 +1,3 @@
> +rcupdate.rcu_self_test=1
> +rcu_nocbs=all
> +rcu_nocb_poll
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-02-25 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 23:04 [PATCH RFC v1 0/4] rcu/nocb: Clean ups and rcutorture test configs Joel Fernandes
2026-02-24 23:04 ` [PATCH RFC v1 1/4] rcu/nocb: Consolidate rcu_nocb_cpu_offload/deoffload functions Joel Fernandes
2026-03-04 15:32 ` Frederic Weisbecker
2026-03-04 17:05 ` Joel Fernandes
2026-02-24 23:04 ` [PATCH RFC v1 2/4] rcu/nocb: Extract nocb_bypass_needs_flush() to reduce duplication Joel Fernandes
2026-03-11 12:58 ` Frederic Weisbecker
2026-02-24 23:04 ` [PATCH RFC v1 3/4] rcutorture: Add NOCB01 config for RCU_LAZY torture testing Joel Fernandes
2026-03-11 13:02 ` Frederic Weisbecker
2026-02-24 23:04 ` [PATCH RFC v1 4/4] rcutorture: Add NOCB02 config for nocb poll mode testing Joel Fernandes
2026-02-25 21:47 ` Paul E. McKenney [this message]
2026-02-26 0:14 ` Joel Fernandes
2026-03-11 13:03 ` Frederic Weisbecker
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=89367e04-7647-4165-be41-385b61aa131b@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=boqun@kernel.org \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=urezki@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