All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Shivank Garg <shivankg@amd.com>
Cc: "jmattson@google.com" <jmattson@google.com>,
	"david@kernel.org" <david@kernel.org>,
	 "ackerleytng@google.com" <ackerleytng@google.com>,
	"pshier@google.com" <pshier@google.com>,
	 "shuah@kernel.org" <shuah@kernel.org>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	 "ricarkol@google.com" <ricarkol@google.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	 "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	 "linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	 "sashiko-bot@kernel.org" <sashiko-bot@kernel.org>
Subject: Re: [PATCH 0/5] KVM: guest_memfd: fix unbind race and NUMA selftests
Date: Mon, 31 Aug 2026 06:34:34 -0700	[thread overview]
Message-ID: <apWC6tyBOsf8LT1t@google.com> (raw)
In-Reply-To: <b95f21c1cb45673351df50dab208ec8dd3e8ca66.camel@amd.com>

On Mon, Aug 31, 2026, Shivank Garg wrote:
> On Sun, 2026-08-23 at 13:36 +0000, Shivank Garg wrote:
> > Split out the guest_memfd folio migration series [1], where migration part
> > needs more discussion. These fixes, reported by Sashiko bot [2][3], are
> > independent of it and can be reviewed on their own.
> > 
> > [1] https://lore.kernel.org/all/20260805-shivank-gmem-migrate-v3-0-00d8bdec4e1d@amd.com 
> > [2] https://lore.kernel.org/all/20260728092027.225CF1F000E9@smtp.kernel.org
> > [3] https://lore.kernel.org/all/20260728091945.EA6C31F000E9@smtp.kernel.org
> > 
> > Signed-off-by: Shivank Garg <shivankg@amd.com>
> > ---
> > Shivank Garg (5):
> >       KVM: guest_memfd: take the invalidate lock when unbinding a dying file
> >       KVM: selftests: fix maxnode arguments in xapic_ipi_test
> >       KVM: selftests: use BITS_PER_TYPE() for NUMA masks
> >       KVM: selftests: add get_numa_mem_nodes()
> >       KVM: selftests: use allowed NUMA nodes in guest_memfd_test
> > 
> >  tools/testing/selftests/kvm/guest_memfd_test.c   | 86 ++++++++++++++++--------
> >  tools/testing/selftests/kvm/include/numaif.h     | 52 ++------------
> >  tools/testing/selftests/kvm/x86/xapic_ipi_test.c | 14 ++--
> >  virt/kvm/guest_memfd.c                           | 23 ++++---
> >  4 files changed, 84 insertions(+), 91 deletions(-)
> > ---
> > base-commit: 2709dd5ae32f0828f386327c76bba9f39f63a1c6
> > change-id: 20260822-shivank-gmem-fix-split-b8a9057cf987
> > 
> > Best regards,
> 
> Hi Sean, Paolo,
> 
> Would you consider queuing this for next (7.4)?

No, I'm expecting a new version based on the discussion in patch 1.

I also don't understand why the selftests changes are bundled in with what appears
to be a completely unrelated bug fix.

  reply	other threads:[~2026-08-31 13:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23 13:36 [PATCH 0/5] KVM: guest_memfd: fix unbind race and NUMA selftests Shivank Garg
2026-08-23 13:36 ` [PATCH 1/5] KVM: guest_memfd: take the invalidate lock when unbinding a dying file Shivank Garg
2026-08-23 13:50   ` sashiko-bot
2026-08-25 21:54     ` Sean Christopherson
2026-08-25 22:13   ` Sean Christopherson
2026-08-26 10:28     ` Garg, Shivank
2026-08-23 13:36 ` [PATCH 2/5] KVM: selftests: fix maxnode arguments in xapic_ipi_test Shivank Garg
2026-08-23 13:36 ` [PATCH 3/5] KVM: selftests: use BITS_PER_TYPE() for NUMA masks Shivank Garg
2026-08-23 13:36 ` [PATCH 4/5] KVM: selftests: add get_numa_mem_nodes() Shivank Garg
2026-08-23 13:47   ` sashiko-bot
2026-08-23 14:22   ` Garg, Shivank
2026-08-23 13:36 ` [PATCH 5/5] KVM: selftests: use allowed NUMA nodes in guest_memfd_test Shivank Garg
2026-08-31  8:24 ` [PATCH 0/5] KVM: guest_memfd: fix unbind race and NUMA selftests Garg, Shivank
2026-08-31 13:34   ` Sean Christopherson [this message]
2026-08-31 14:22     ` Garg, Shivank

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=apWC6tyBOsf8LT1t@google.com \
    --to=seanjc@google.com \
    --cc=ackerleytng@google.com \
    --cc=david@kernel.org \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=pshier@google.com \
    --cc=ricarkol@google.com \
    --cc=sashiko-bot@kernel.org \
    --cc=shivankg@amd.com \
    --cc=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.