From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Shivank Garg <shivankg@amd.com>
Subject: Re: [PATCH 0/7] KVM: selftests: Fix maxnodes bugs and cleanup related code
Date: Mon, 21 Sep 2026 07:05:42 -0700 [thread overview]
Message-ID: <178999926338.754170.2692559524716409337.b4-ty@google.com> (raw)
In-Reply-To: <20260903001625.2792367-1-seanjc@google.com>
On Wed, 02 Sep 2026 17:16:18 -0700, Sean Christopherson wrote:
> This is a spin-off of Shivank's series[*] to fix "flaws" in KVM selftests
> handling of @maxnode in various sycalls. In quote because the flaw is that
> KVM selftests followed the docs, and the kernel has a longstanding, poorly
> documented off-by-one bug.
>
> Along the way, massage the xAPIC IPI test to automatically run its page
> migration testcases when possible, because that's the entire reason the
> test exists.
>
> [...]
Applied to kvm-x86 selftests, thanks!
[1/7] KVM: selftests: Account for kernel's off-by-one bug in NUMA node syscalls
https://github.com/kvm-x86/linux/commit/be3c6888e1ab
[2/7] KVM: selftests: Fix maxnode argument to migrate_pages() in xapic_ipi_test
https://github.com/kvm-x86/linux/commit/8883d2410c45
[3/7] KVM: selftests: use BITS_PER_TYPE() for NUMA masks
https://github.com/kvm-x86/linux/commit/d2dde5c387fc
[4/7] KVM: selftests: Compute node masks on-demand in xAPIC IPI test
https://github.com/kvm-x86/linux/commit/3a2a37d2d48e
[5/7] KVM: selftests: Add common helper to get mask+number of usable memory NUMA nodes
https://github.com/kvm-x86/linux/commit/0be096bbc9cc
[6/7] KVM: selftests: Automatically run xAPIC IPI migration test when possible
https://github.com/kvm-x86/linux/commit/92ed4d5c78fd
[7/7] KVM: selftests: Skip xAPIC IPI migration test when forced but unsupported
https://github.com/kvm-x86/linux/commit/d5aa06fbfec2
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2026-09-21 14:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 0:16 [PATCH 0/7] KVM: selftests: Fix maxnodes bugs and cleanup related code Sean Christopherson
2026-09-03 0:16 ` [PATCH 1/7] KVM: selftests: Account for kernel's off-by-one bug in NUMA node syscalls Sean Christopherson
2026-09-06 10:08 ` Garg, Shivank
2026-09-03 0:16 ` [PATCH 2/7] KVM: selftests: Fix maxnode argument to migrate_pages() in xapic_ipi_test Sean Christopherson
2026-09-03 0:16 ` [PATCH 3/7] KVM: selftests: use BITS_PER_TYPE() for NUMA masks Sean Christopherson
2026-09-03 0:16 ` [PATCH 4/7] KVM: selftests: Compute node masks on-demand in xAPIC IPI test Sean Christopherson
2026-09-06 17:05 ` Garg, Shivank
2026-09-03 0:16 ` [PATCH 5/7] KVM: selftests: Add common helper to get mask+number of usable memory NUMA nodes Sean Christopherson
2026-09-06 17:53 ` Garg, Shivank
2026-09-03 0:16 ` [PATCH 6/7] KVM: selftests: Automatically run xAPIC IPI migration test when possible Sean Christopherson
2026-09-06 18:01 ` Garg, Shivank
2026-09-03 0:16 ` [PATCH 7/7] KVM: selftests: Skip xAPIC IPI migration test when forced but unsupported Sean Christopherson
2026-09-06 18:13 ` Garg, Shivank
2026-09-21 14:05 ` 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=178999926338.754170.2692559524716409337.b4-ty@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=shivankg@amd.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 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.