From: "Naveen N Rao (AMD)" <naveen@kernel.org>
To: <kvm@vger.kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Vasant Hegde <vasant.hegde@amd.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: [RFC kvm-unit-tests PATCH 0/4] x86/apic: SVM AVIC tests and some cleanups
Date: Tue, 25 Feb 2025 16:10:48 +0530 [thread overview]
Message-ID: <cover.1740479886.git.naveen@kernel.org> (raw)
The first patch is a small cleanup. The next two patches update tests to
disable PIT so that SVM AVIC can be exercized. The last patch adds a
test for x1apic-split.
The last patch causes aliased apic_id ipi test to fail with older qemu
versions. Qemu v6.2 and before used to enable
KVM_X2APIC_API_USE_32BIT_IDS KVM quirk in some scenarios, and this was
changed in commit dc89f32d92bb ("target/i386: Fix sanity check on max
APIC ID / X2APIC enablement") to be enabled only if there are > 255
vcpus. The KUT test does talk about this assumption in a comment:
/*
* By default, KVM doesn't follow the x86 APIC architecture for aliased
* APIC IDs if userspace has enabled KVM_X2APIC_API_USE_32BIT_IDS.
* If x2APIC is supported, assume the userspace VMM has enabled 32-bit
* IDs and thus activated KVM's quirk. Delete this code to run the
* aliasing test on x2APIC CPUs, e.g. to run it on bare metal.
*/
That looks to suggest that this is an expected failure, but it would be
good to get confirmation on the same.
Thanks,
Naveen
Naveen N Rao (AMD) (4):
x86/apic: Move ioapic tests together and add them to apic test group
x86/apic: Disable PIT for x2apic test to allow SVM AVIC to be tested
x86/apic: Disable PIT for ioapic test to allow SVM AVIC to be tested
x86/apic: Add test for xapic-split
x86/unittests.cfg | 27 ++++++++++++++++++---------
1 file changed, 18 insertions(+), 9 deletions(-)
base-commit: 699264f5ef8129c60e9db7c281e572016ad41a45
--
2.48.1
next reply other threads:[~2025-02-25 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 10:40 Naveen N Rao (AMD) [this message]
2025-02-25 10:40 ` [RFC kvm-unit-tests PATCH 1/4] x86/apic: Move ioapic tests together and add them to apic test group Naveen N Rao (AMD)
2025-02-25 10:40 ` [RFC kvm-unit-tests PATCH 2/4] x86/apic: Disable PIT for x2apic test to allow SVM AVIC to be tested Naveen N Rao (AMD)
2025-06-03 23:53 ` Sean Christopherson
2025-02-25 10:40 ` [RFC kvm-unit-tests PATCH 3/4] x86/apic: Disable PIT for ioapic " Naveen N Rao (AMD)
2025-02-25 10:40 ` [RFC kvm-unit-tests PATCH 4/4] x86/apic: Add test for xapic-split Naveen N Rao (AMD)
2025-03-04 20:33 ` Sean Christopherson
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=cover.1740479886.git.naveen@kernel.org \
--to=naveen@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@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.