Re: [kvm-unit-tests PATCH 03/10] x86: Use "safe" terminology instead of "checking"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 9/6/2022 7:52 am, Sean Christopherson wrote:
@@ -138,13 +138,13 @@ static void test_no_xsave(void)
      printf("Illegal instruction testing:\n");
cr4 = read_cr4();
-    report(write_cr4_checking(cr4 | X86_CR4_OSXSAVE) == GP_VECTOR,
+    report(write_cr4_safe(cr4 | X86_CR4_OSXSAVE) == GP_VECTOR,
             "Set OSXSAVE in CR4 - expect #GP");
report(xgetbv_checking(XCR_XFEATURE_ENABLED_MASK, &xcr0) == UD_VECTOR,
             "Execute xgetbv - expect #UD");

Oops, xgetbv_checking() has not been renamed to xgetbv_safe().

- report(xsetbv_checking(XCR_XFEATURE_ENABLED_MASK, 0x3) == UD_VECTOR,
+    report(xsetbv_safe(XCR_XFEATURE_ENABLED_MASK, 0x3) == UD_VECTOR,
             "Execute xsetbv - expect #UD");
  }



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux