From: Uladzislau Rezki <urezki@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, rostedt@goodmis.org
Subject: Re: [PATCH 0/4] Torture-test updates for v7.2
Date: Fri, 8 May 2026 19:06:10 +0200 [thread overview]
Message-ID: <af4YAggY4_aj_Qxr@milan> (raw)
In-Reply-To: <1e506157-35a8-4ea9-8bb6-cfe899d81e6e@paulmck-laptop>
On Thu, May 07, 2026 at 09:57:11AM -0700, Paul E. McKenney wrote:
> Hello!
>
> This series contains torture-test updates for v7.2:
>
> 1. Fully test lazy RCU.
>
> 2. Add torture_sched_set_normal() for user-specified nice values.
>
> 3. Improve kvm-series.sh header comment.
>
> 4. Allow "norm" abbreviation for "normal".
>
> Thanx, Paul
>
> ------------------------------------------------------------------------
>
> b/include/linux/torture.h | 1
> b/kernel/rcu/rcu.h | 7
> b/kernel/rcu/rcutorture.c | 21 +-
> b/kernel/rcu/tree_plugin.h | 32 +++
> b/kernel/torture.c | 16 +
> b/tools/testing/selftests/rcutorture/bin/kvm-series.sh | 11 -
> b/tools/testing/selftests/rcutorture/bin/torture.sh | 2
> kernel/rcu/rcutorture.c | 160 +++++++++--------
> 8 files changed, 168 insertions(+), 82 deletions(-)
>
This i took.
--
Uladzislau Rezki
prev parent reply other threads:[~2026-05-08 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 16:57 [PATCH 0/4] Torture-test updates for v7.2 Paul E. McKenney
2026-05-07 16:57 ` [PATCH 1/6] rcutorture: Fully test lazy RCU Paul E. McKenney
2026-05-07 16:57 ` [PATCH 2/6] torture: Add torture_sched_set_normal() for user-specified nice values Paul E. McKenney
2026-05-07 16:57 ` [PATCH 3/6] torture: Improve kvm-series.sh header comment Paul E. McKenney
2026-05-07 16:57 ` [PATCH 4/6] torture: Allow "norm" abbreviation for "normal" Paul E. McKenney
2026-05-08 17:06 ` Uladzislau Rezki [this message]
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=af4YAggY4_aj_Qxr@milan \
--to=urezki@gmail.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