From: Joel Fernandes <joelagnelf@nvidia.com>
To: linux-kernel@vger.kernel.org
Cc: Joel Fernandes <joelagnelf@nvidia.com>
Subject: [PATCH v3 0/2] New rcutorture candidate commits for 6.16
Date: Thu, 10 Apr 2025 11:03:26 -0400 [thread overview]
Message-ID: <20250410150329.3807285-1-joelagnelf@nvidia.com> (raw)
The gpwrap one is is v3 where I just fixed the hrtimer_init() since v2.
The ARM64 image check is a new one, but is a small change and required for me
to do large tests with SRCU.
(These are only the new commits, the existing ones in my for-next branch for
rcutorture will be sent separately next week).
Joel Fernandes (2):
rcutorture: Perform more frequent testing of ->gpwrap
rcutorture: Fix issue with re-using old images on ARM64
kernel/rcu/rcu.h | 4 ++
kernel/rcu/rcutorture.c | 67 ++++++++++++++++++-
kernel/rcu/tree.c | 34 +++++++++-
kernel/rcu/tree.h | 1 +
.../rcutorture/bin/kvm-test-1-run.sh | 2 +-
5 files changed, 104 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2025-04-10 15:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 15:03 Joel Fernandes [this message]
2025-04-10 15:03 ` [PATCH v3 1/2] rcutorture: Perform more frequent testing of ->gpwrap Joel Fernandes
2025-04-10 18:29 ` Paul E. McKenney
2025-04-10 18:54 ` Paul E. McKenney
2025-04-11 1:47 ` Paul E. McKenney
2025-04-11 5:36 ` [v3,1/2] " Joel Fernandes
2025-04-11 19:18 ` Paul E. McKenney
2025-04-14 12:07 ` Joel Fernandes
2025-04-14 14:24 ` Paul E. McKenney
2025-04-14 14:56 ` Joel Fernandes
2025-04-14 16:17 ` Paul E. McKenney
2025-04-11 5:36 ` Joel Fernandes
2025-04-14 15:05 ` [PATCH v3 1/2] " Joel Fernandes
2025-04-16 0:19 ` Paul E. McKenney
2025-04-16 11:19 ` Joel Fernandes
2025-04-20 0:21 ` Paul E. McKenney
2025-04-20 2:40 ` [v3,1/2] rcutorture: Perform more frequent testing of ->gpwrap Joel Fernandes
2025-04-20 18:04 ` Paul E. McKenney
2025-04-10 15:03 ` [PATCH v3 2/2] rcutorture: Fix issue with re-using old images on ARM64 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=20250410150329.3807285-1-joelagnelf@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®