From: "Neeraj Upadhyay (AMD)" <neeraj.iitr10@gmail.com>
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
rostedt@goodmis.org, paulmck@kernel.org, Neeraj.Upadhyay@amd.com
Subject: [PATCH rcu 0/4] RCU/lock torture updates for v6.8
Date: Tue, 12 Dec 2023 23:03:34 +0530 [thread overview]
Message-ID: <20231212173334.GA11572@neeraj.linux> (raw)
Hello,
This series contains torture-test updates:
1. Increase Hamming distance between call_rcu_chain and
rcu_call_chains.
2. add nolibc init support for mips, ppc and rv64, courtesy of
Thomas Weißschuh.
3. Add mid-sized stall to TREE07.
4. Add fqs_holdoff check before fqs_task is created, courtesy
of Zqiang.
Thanks
Neeraj
------------------------------------------------------------------------
kernel/locking/locktorture.c | 18 +++++++++---------
kernel/rcu/rcutorture.c | 4 +++-
tools/testing/selftests/rcutorture/bin/mkinitrd.sh | 5 ++++-
tools/testing/selftests/rcutorture/configs/rcu/TREE07.boot | 3 +++
4 files changed, 19 insertions(+), 11 deletions(-)
next reply other threads:[~2023-12-12 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 17:33 Neeraj Upadhyay (AMD) [this message]
2023-12-12 17:34 ` [PATCH rcu 1/4] locktorture: Increase Hamming distance between call_rcu_chain and rcu_call_chains Neeraj Upadhyay (AMD)
2023-12-12 17:34 ` [PATCH rcu 2/4] rcutorture: add nolibc init support for mips, ppc and rv64 Neeraj Upadhyay (AMD)
2023-12-12 17:34 ` [PATCH rcu 3/4] rcutorture: Add mid-sized stall to TREE07 Neeraj Upadhyay (AMD)
2023-12-12 17:34 ` [PATCH rcu 4/4] rcutorture: Add fqs_holdoff check before fqs_task is created Neeraj Upadhyay (AMD)
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=20231212173334.GA11572@neeraj.linux \
--to=neeraj.iitr10@gmail.com \
--cc=Neeraj.Upadhyay@amd.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).