mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joel Fernandes <joelagnelf@nvidia.com>
To: Joel Fernandes <joelagnelf@nvidia.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/2] My new rcutorture patches for 6.15
Date: Tue, 15 Apr 2025 09:40:34 -0400	[thread overview]
Message-ID: <78618417-3c33-4417-b72d-6aad0104a042@nvidia.com> (raw)
In-Reply-To: <20250415133622.1563137-1-joelagnelf@nvidia.com>


On 4/15/2025 9:36 AM, Joel Fernandes wrote:
> The gpwrap one is is v4 where I just fixed the hrtimer_init() since v2.
> 
> The ARM64 image check is now in my for-next branch, it is required to do large
> scale tests with SRCU.
> 
> (These are only the new commits, the existing ones in my for-next branch for
> rcutorture will be sent separately once we figure out which one of them is
> causing SRCU issues).
> 
> 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                       | 68 ++++++++++++++++++-
>  kernel/rcu/tree.c                             | 34 +++++++++-
>  kernel/rcu/tree.h                             |  1 +
>  .../rcutorture/bin/kvm-test-1-run.sh          |  2 +-
>  6 files changed, 107 insertions(+), 6 deletions(-)
> 

Oops, s/15/16/ in subject :)

 - Joel


      parent reply	other threads:[~2025-04-15 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 13:36 Joel Fernandes
2025-04-15 13:36 ` [PATCH v4 1/2] rcutorture: Perform more frequent testing of ->gpwrap Joel Fernandes
2025-04-15 13:36 ` [PATCH v4 2/2] rcutorture: Fix issue with re-using old images on ARM64 Joel Fernandes
2025-04-15 13:46   ` Joel Fernandes
2025-04-15 13:40 ` Joel Fernandes [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=78618417-3c33-4417-b72d-6aad0104a042@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®