mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Garg, Shivank" <shivankg@amd.com>
To: "seanjc@google.com" <seanjc@google.com>
Cc: "jmattson@google.com" <jmattson@google.com>,
	"fuad.tabba@linux.dev" <fuad.tabba@linux.dev>,
	"david@kernel.org" <david@kernel.org>,
	"ackerleytng@google.com" <ackerleytng@google.com>,
	"pshier@google.com" <pshier@google.com>,
	"shuah@kernel.org" <shuah@kernel.org>,
	"suzuki.poulose@arm.com" <suzuki.poulose@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"ricarkol@google.com" <ricarkol@google.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"steven.price@arm.com" <steven.price@arm.com>
Subject: Re: [PATCH RESEND v3 0/4] KVM: guest_memfd: fix NUMA selftests
Date: Fri, 20 Nov 2026 16:13:59 +0000	[thread overview]
Message-ID: <c0cc9c1de5c676402304f9610f8552bb4510ce49.camel@amd.com> (raw)
In-Reply-To: <awBUlv3ItZiyZvlS@seanjc-mac.roam.internal>

On Fri, 2026-11-20 at 06:09 -0800, Sean Christopherson wrote:
> On Fri, Nov 20, 2026, Shivank Garg wrote:
> > NUMA selftests in guest_memfd_test assumes that node 0 and 1 exist and
> > have memory. However, nodes can be sparse or memoryless which would
> > break this selftest.  Select the nodes from MPOL_F_MEMS_ALLOWED instead.
> > 
> > Based on kvm-x86/next.
> > 
> > Tested on bare metal and in QEMU. Without this series, the test fails
> > with EINVAL when node 0 or node 1 is not an allowed memory node. With it,
> > the test passes for any set of allowed NUMA nodes.
> > 
> > RESEND:
> > - Rebase on kvm-x86/next. No code changes.
> 
> If there are no code changes, then there's no need to rebase.  Please use
> RESEND if and only if you are sending the *exact* same patches/emails, e.g.
> because you missed a To: or Cc:, or a mail got dropped by your server, etc.
> 
> If you want to ping a patch/series, just ping.  v3 is sitting in my TODO folder
> and applies cleanly, i.e. there was no need to send the entire series again.


Got it, sorry for the noise.
I did not know about this and will keep it in mind for next time.

Thanks,
Shivank

      reply	other threads:[~2026-11-20 16:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20 11:28 Shivank Garg
2026-11-20 11:28 ` [PATCH RESEND v3 1/4] KVM: selftests: Prepare guest_memfd_test for arbitrary NUMA nodes Shivank Garg
2026-11-20 11:28 ` [PATCH RESEND v3 2/4] KVM: selftests: Use an allowed memory node in test_mbind() Shivank Garg
2026-11-20 11:28 ` [PATCH RESEND v3 3/4] KVM: selftests: Use allowed memory nodes in test_numa_allocation() Shivank Garg
2026-11-20 11:28 ` [PATCH RESEND v3 4/4] KVM: selftests: Drop unused sysfs NUMA helpers Shivank Garg
2026-11-20 14:09 ` [PATCH RESEND v3 0/4] KVM: guest_memfd: fix NUMA selftests Sean Christopherson
2026-11-20 16:13   ` Garg, Shivank [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=c0cc9c1de5c676402304f9610f8552bb4510ce49.camel@amd.com \
    --to=shivankg@amd.com \
    --cc=ackerleytng@google.com \
    --cc=david@kernel.org \
    --cc=fuad.tabba@linux.dev \
    --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=seanjc@google.com \
    --cc=shuah@kernel.org \
    --cc=steven.price@arm.com \
    --cc=suzuki.poulose@arm.com \
    /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®