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 3/4] x86/svm: Replace #UD on failure in LBRV tests with proper report()s
Date: Tue, 4 Nov 2025 19:30:15 +0000 [thread overview]
Message-ID: <20251104193016.3408754-4-yosry.ahmed@linux.dev> (raw)
In-Reply-To: <20251104193016.3408754-1-yosry.ahmed@linux.dev>
In LBRV tests, failures in the guest trigger a #UD and does not convey
useful debugging info (i.e. expected and actual values of MSRs). Replace
them with proper report() calls.
Admittedly, it is unclear why the choice of #UD was made given that
report() works fine in the guest.
Signed-off-by: Yosry Ahmed <yosry.ahmed@linux.dev>
---
x86/svm_tests.c | 17 +++++++++--------
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/x86/svm_tests.c b/x86/svm_tests.c
index 2981f459032cb..8d309860e76e5 100644
--- a/x86/svm_tests.c
+++ b/x86/svm_tests.c
@@ -3017,16 +3017,17 @@ do { \
TEST_EXPECT_EQ((u64)to_expected, amd_get_lbr_rip(MSR_IA32_LASTBRANCHTOIP)); \
} while (0)
-/*
- * FIXME: Do something other than generate an exception to communicate failure.
- * Debugging without expected vs. actual is an absolute nightmare.
- */
#define GUEST_CHECK_LBR(from_expected, to_expected) \
do { \
- if ((u64)(from_expected) != amd_get_lbr_rip(MSR_IA32_LASTBRANCHFROMIP)) \
- asm volatile("ud2"); \
- if ((u64)(to_expected) != amd_get_lbr_rip(MSR_IA32_LASTBRANCHTOIP)) \
- asm volatile("ud2"); \
+ u64 from_ip = amd_get_lbr_rip(MSR_IA32_LASTBRANCHFROMIP); \
+ u64 to_ip = amd_get_lbr_rip(MSR_IA32_LASTBRANCHTOIP); \
+ \
+ report((u64)(from_expected) == from_ip, \
+ "Expected MSR_IA32_LASTBRANCHFROMIP: 0x%lx, found: 0x%lx", \
+ (u64)from_expected, from_ip); \
+ report((u64)(to_expected) == to_ip, \
+ "Expected MSR_IA32_LASTBRANCHTOIP: 0x%lx, found: 0x%lx", \
+ (u64)to_expected, to_ip); \
} while (0)
#define REPORT_GUEST_LBR_ERROR(vmcb) \
--
2.51.2.1026.g39e6a42477-goog
next prev parent 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 [kvm-unit-tests 0/4] Misc fixups/cleanups for nested tests Yosry Ahmed
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 ` Yosry Ahmed [this message]
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-4-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