From: Joel Fernandes <joelagnelf@nvidia.com>
To: paulmck@kernel.org
Cc: rcu <rcu@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel-team <kernel-team@meta.com>, rostedt <rostedt@goodmis.org>
Subject: Re: [v2,05/12] rcutorture: Add tests for SRCU up/down reader primitives
Date: Tue, 8 Apr 2025 18:05:19 -0400 [thread overview]
Message-ID: <702640f3-170c-41be-861c-7ec436a02dad@nvidia.com> (raw)
In-Reply-To: <8ee04d0a-dc22-4eb1-8c22-1777f94fd9fb@paulmck-laptop>
On 4/8/2025 4:58 PM, Paul E. McKenney wrote:
> On Tue, Apr 08, 2025 at 08:18:05PM -0000, Joel Fernandes wrote:
>> Hello, Paul,
>>
>> On Tue, 8 Apr 2025 20:16:08 GMT, "Paul E. McKenney" wrote:
>>> This commit adds a new rcutorture.n_up_down kernel boot parameter
>>> that specifies the number of outstanding SRCU up/down readers, which
>>> begin in kthread context and end in an hrtimer handler. There is a new
>>> kthread ("rcu_torture_updown") that scans an per-reader array looking
>>> for elements whose readers have ended. This kthread sleeps between one
>>> and two milliseconds between consecutive scans.
>>>
>>> [ paulmck: Apply kernel test robot feedback. ]
>>> [ paulmck: Apply Z qiang feedback. ]
>>>
>> [...]
>>> + for (i = 0; i < n_up_down; i++) {
>>> + init_rcu_torture_one_read_state(&updownreaders[i].rtorsu_rtors, rand);
>>> + hrtimer_init(&updownreaders[i].rtorsu_hrt, CLOCK_MONOTONIC,
>>> + HRTIMER_MODE_REL | HRTIMER_MODE_SOFT);
>>
>> This will now fail to build and needs the following: I will squash it into my
>> for-next branch into this patch, but let me know if you prefer to provide an
>> update.
>
> Please feel free to squash it in with your "[]" tag like shown above.
Yep done already. :-)
>
> As you say, you will be sending them all out soon enough anyway. ;-)
True. ;-)
>
> My plan is to rebase on your stack once you finish your first long-form
> round of testing.
Perfect, my first long-form test should be done by tomorrow AM.
- Joel
>
> Thanx, Paul
>
>> Fix build error by converting hrtimer_init to hrtimer_setup, see:
>> https://lore.kernel.org/all/174384280127.31282.2714486346304643188.tip-bot2@tip-bot2/
>>
>> diff --git a/kernel/rcu/rcutorture.c b/kernel/rcu/rcutorture.c
>> index 4f0a00a8bdee..14a22ef3b56f 100644
>> --- a/kernel/rcu/rcutorture.c
>> +++ b/kernel/rcu/rcutorture.c
>> @@ -2480,9 +2480,8 @@ static int rcu_torture_updown_init(void)
>> }
>> for (i = 0; i < n_up_down; i++) {
>> init_rcu_torture_one_read_state(&updownreaders[i].rtorsu_rtors, rand);
>> - hrtimer_init(&updownreaders[i].rtorsu_hrt, CLOCK_MONOTONIC,
>> - HRTIMER_MODE_REL | HRTIMER_MODE_SOFT);
>> - updownreaders[i].rtorsu_hrt.function = rcu_torture_updown_hrt;
>> + hrtimer_setup(&updownreaders[i].rtorsu_hrt,
>> rcu_torture_updown_hrt, CLOCK_MONOTONIC,
>> + HRTIMER_MODE_REL | HRTIMER_MODE_SOFT);
>> torture_random_init(&updownreaders[i].rtorsu_trs);
>> init_rcu_torture_one_read_state(&updownreaders[i].rtorsu_rtors,
>> &updownreaders[i].rtorsu_trs);
>>
>> Thanks.
next prev parent reply other threads:[~2025-04-08 22:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 21:02 [PATCH v2 0/12] Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 01/12] rcutorture: Make srcu_lockdep.sh check kernel Kconfig Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 02/12] rcutorture: Make srcu_lockdep.sh check reader-conflict handling Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 03/12] rcutorture: Split out beginning and end from rcu_torture_one_read() Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 04/12] rcutorture: Make torture.sh --do-rt use CONFIG_PREEMPT_RT Paul E. McKenney
2025-04-02 7:42 ` Sebastian Andrzej Siewior
2025-04-02 18:51 ` Paul E. McKenney
2025-04-07 19:12 ` [PATCH v3 4/12] " Paul E. McKenney
2025-04-08 14:29 ` [v3,4/12] " Joel Fernandes
2025-04-08 16:20 ` Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 05/12] rcutorture: Add tests for SRCU up/down reader primitives Paul E. McKenney
2025-04-08 20:18 ` [v2,05/12] " Joel Fernandes
2025-04-08 20:58 ` Paul E. McKenney
2025-04-08 22:05 ` Joel Fernandes [this message]
2025-04-08 22:21 ` Paul E. McKenney
2025-04-15 17:16 ` [PATCH v2 05/12] " Joel Fernandes
2025-04-15 17:59 ` Paul E. McKenney
2025-04-15 21:15 ` Paul E. McKenney
2025-04-16 1:14 ` Joel Fernandes
2025-04-16 3:55 ` Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 06/12] rcutorture: Pull rcu_torture_updown() loop body into new function Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 07/12] rcutorture: Comment invocations of tick_dep_set_task() Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 08/12] rcutorture: Complain if an ->up_read() is delayed more than 10 seconds Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 09/12] rcutorture: Check for ->up_read() without matching ->down_read() Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 10/12] checkpatch: Deprecate srcu_read_lock_lite() and srcu_read_unlock_lite() Paul E. McKenney
2025-04-01 6:53 ` Joe Perches
2025-04-01 14:05 ` Paul E. McKenney
2025-04-02 3:48 ` Joe Perches
2025-04-02 4:23 ` Paul E. McKenney
2025-04-02 4:49 ` Joe Perches
2025-04-02 14:12 ` Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 11/12] torture: Add --do-{,no-}normal to torture.sh Paul E. McKenney
2025-03-31 21:03 ` [PATCH v2 12/12] torture: Add testing of RCU's Rust bindings " Paul E. McKenney
2025-04-02 14:45 ` [PATCH v2 0/12] Joel Fernandes
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=702640f3-170c-41be-861c-7ec436a02dad@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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