From: Yosry Ahmed <yosry.ahmed@linux.dev>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Jim Mattson <jmattson@google.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Yosry Ahmed <yosry.ahmed@linux.dev>
Subject: [kvm-unit-tests 0/4] Misc fixups/cleanups for nested tests
Date: Tue, 4 Nov 2025 19:30:12 +0000 [thread overview]
Message-ID: <20251104193016.3408754-1-yosry.ahmed@linux.dev> (raw)
A group of misc cleanups and fixups for SVM and VMX tests.
Disclaimer for patch 3: I have no idea why #UD was used to convey
failure from the guest when report() is usable, so I might have missed
something there.
Disclaimer for patch 4: I did not look too closely into why the flake is
happening. It seemed like there was an adhoc approach to stabilize the
test (shift duration by 24 bits), so I just made the necessary
adjustment to make the test stable on Turin.
This series is based on a different SVM series to avoid conflicts:
https://lore.kernel.org/kvm/20251028221213.1937120-1-yosry.ahmed@linux.dev/
Yosry Ahmed (4):
x86/vmx: Skip vmx_pf_exception_test_fep early if FEP is not available
x86/svm: Print SVM test names before running tests
x86/svm: Replace #UD on failure in LBRV tests with proper report()s
x86/svm: Deflake svm_tsc_scale_test
x86/svm.c | 1 +
x86/svm_tests.c | 19 ++++++++++---------
x86/vmx_tests.c | 5 ++++-
3 files changed, 15 insertions(+), 10 deletions(-)
--
2.51.2.1026.g39e6a42477-goog
next reply other threads:[~2025-11-04 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 19:30 Yosry Ahmed [this message]
2025-11-04 19:30 ` [kvm-unit-tests 1/4] x86/vmx: Skip vmx_pf_exception_test_fep early if FEP is not available Yosry Ahmed
2025-11-04 19:30 ` [kvm-unit-tests 2/4] x86/svm: Print SVM test names before running tests Yosry Ahmed
2025-11-04 19:30 ` [kvm-unit-tests 3/4] x86/svm: Replace #UD on failure in LBRV tests with proper report()s Yosry Ahmed
2025-11-04 19:30 ` [kvm-unit-tests 4/4] x86/svm: Deflake svm_tsc_scale_test Yosry Ahmed
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=20251104193016.3408754-1-yosry.ahmed@linux.dev \
--to=yosry.ahmed@linux.dev \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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