From: Sean Christopherson <seanjc@google.com>
To: Shivank Garg <shivankg@amd.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
David Hildenbrand <david@kernel.org>,
Shuah Khan <shuah@kernel.org>, Jim Mattson <jmattson@google.com>,
Peter Shier <pshier@google.com>,
Ricardo Koller <ricarkol@google.com>,
Ackerley Tng <ackerleytng@google.com>,
Fuad Tabba <fuad.tabba@linux.dev>,
Steven Price <steven.price@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v3 0/4] KVM: guest_memfd: fix NUMA selftests
Date: Fri, 20 Nov 2026 06:09:26 -0800 [thread overview]
Message-ID: <awBUlv3ItZiyZvlS@seanjc-mac.roam.internal> (raw)
In-Reply-To: <20261120-gmem-selftests-fix-v3-0-d94ffe17ead6@amd.com>
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.
prev parent reply other threads:[~2026-11-20 14:09 UTC|newest]
Thread overview: 6+ 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 ` Sean Christopherson [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=awBUlv3ItZiyZvlS@seanjc-mac.roam.internal \
--to=seanjc@google.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=shivankg@amd.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®