Explicitly state that the invalid limit tests are testing a limit greater than 0xffff. Simply stating the field name is not helpful since it's already printed on failure. Signed-off-by: Sean Christopherson <seanjc@xxxxxxxxxx> --- x86/vmx_tests.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/x86/vmx_tests.c b/x86/vmx_tests.c index 94ab499..1097a53 100644 --- a/x86/vmx_tests.c +++ b/x86/vmx_tests.c @@ -8205,7 +8205,7 @@ static void vmx_guest_state_area_test(void) for (i = 16; i <= 31; i++) { u32 tmp = guest_desc_limit_saved | (1ull << i); vmcs_write(GUEST_LIMIT_GDTR, tmp); - test_guest_state("GUEST_LIMIT_GDTR", true, tmp, "GUEST_LIMIT_GDTR"); + test_guest_state("GDT.limit > 0xffff", true, tmp, "GUEST_LIMIT_GDTR"); } vmcs_write(GUEST_LIMIT_GDTR, guest_desc_limit_saved); @@ -8213,7 +8213,7 @@ static void vmx_guest_state_area_test(void) for (i = 16; i <= 31; i++) { u32 tmp = guest_desc_limit_saved | (1ull << i); vmcs_write(GUEST_LIMIT_IDTR, tmp); - test_guest_state("GUEST_LIMIT_IDTR", true, tmp, "GUEST_LIMIT_IDTR"); + test_guest_state("IDT.limit > 0xffff", true, tmp, "GUEST_LIMIT_IDTR"); } vmcs_write(GUEST_LIMIT_IDTR, guest_desc_limit_saved); -- 2.30.0.478.g8a0d178c01-goog