nVMX: Improve IA32_DEBUGCTLMSR test on debug controls
v2 cover nVMX: Improve IA32_DEBUGCTLMSR test on debug controls
Current nested debugctls test focuses on DR7 value and fakes the result of IA32_DEBUGCTLMSR in comment. Although the test can pass because DR7 is the only criterion to determine the result, there are some error messages appearing in dmesg due to accessing to BTF | LBR bits in IA32_DEBUGCTLMSR with report_ignored_msrs KVM parameter enabled.
Clean up the old test so that it focuses on DR7, then add separate tests for DEBUGCTLMSR bits that are actually supported and can be validated during VMX transitions.
Tested on:
Emerald Rapids:
vmx_bus_lock_detect_test PASS
vmx_rtm_test PASS
vmx_legacy_lbr_test SKIPSkylake:
vmx_bus_lock_detect_test SKIP
vmx_rtm_test PASS
vmx_legacy_lbr_test PASSChanges since v1:
- Modify the commit message in patch 1 (Xiaoyao)
- Add dedicated tests (for BUS_LOCK_DETECT and LBR) covering the DEBUGCTL reads and writes during VMX transitions (Sean)
- Add one additional test for RTM_DEBUG bit that was not mentioned in v1.
- https://lore.kernel.org/kvm/[email protected]/
Chenyi Qiang (4):
nVMX: Remove the IA32_DEBUGCTLMSR access in debugctls test
nVMX: Validate DEBUGCTLMSR_BUS_LOCK_DETECT states during VMX
transitions
nVMX: Validate DEBUGCTLMSR_RTM_DEBUG states during VMX transitions
nVMX: Validate DEBUGCTLMSR_LBR states during VMX transitions
lib/x86/msr.h | 2 + x86/unittests.cfg | 25 +++++++ x86/vmx_tests.c | 175 +++++++++++++++++++++++++++++++++++++--------- 3 files changed, 170 insertions(+), 32 deletions(-)
Signature · 1 line
2.43.5
PATCH v2 1/4 nVMX: Remove the IA32_DEBUGCTLMSR access in debugctls test
"debug controls" test was added by commit dc5c01f17b1a ("VMX: Test behavior on set and cleared save/load debug controls") to verify that "VM-Entry load debug controls" and "VM-Exit save debug controls" are correctly emulated by KVM for nested VMX. But due to the limitation that KVM didn't support MSR_IA32_DEBUGCTL for guest at that time, the test commented out all the value comparison of MSR_IA32_DEBUGCTL and leave it to future when KVM supports the MSR.
The test doesn't check the functionality of save/restore guest MSR_IA32_DEBUGCTL on vm-exit/entry, but it keeps the write of MSR_IA32_DEBUGCTL. It leads to
kvm_intel: kvm [18663]: vcpu0, guest rIP: 0x407de7 Unhandled WRMSR(0x1d9) = 0x1
kvm_intel: kvm [18663]: vcpu0, guest rIP: 0x0 Unhandled WRMSR(0x1d9) = 0x2
kvm_intel: kvm [18663]: vcpu0, guest rIP: 0x40936f Unhandled WRMSR(0x1d9) = 0x3
kvm_intel: kvm [18663]: vcpu0, guest rIP: 0x40cf09 Unhandled WRMSR(0x1d9) = 0x1
kvm_intel: kvm [18663]: vcpu0, guest rIP: 0x40940d Unhandled WRMSR(0x1d9) = 0x3
to the kernel log. Though it doesn't break the test, the log confuses people to think something wrong happened in the test case.
Current KVM doesn't support some bits of MSR_IA32_DEBUGCTL but they depend on the vcpu model exposed. To simplify the case and eliminate the confusing "Unhandled WRMSR(0x1d9)" log, remove the MSR_IA32_DEBUGCTL logic in the test and make it concentrate only on DR7. Following patch will bring back MSR_IA32_DEBUGCTL separately.
---
Changes in v2:
- Rewrite of commit message by Xiaoyao.
- Add RB from Xiaoyao.
--- x86/vmx_tests.c | 46 ++++++++++++++-------------------------------- 1 file changed, 14 insertions(+), 32 deletions(-)
x86/vmx_tests.c +14 -32
@@ -1856,21 +1856,18 @@ static int nmi_hlt_exit_handler(union exit_reason exit_reason) } -static int dbgctls_init (struct vmcs *vmcs) +static int dbgctls_dr7_init (struct vmcs *vmcs) {u64 dr7 =0x402 ;u64 zero =0 ; -msr_bmp_init (); asmvolatile ("mov %0,%%dr0\n\t" "mov %0,%%dr1\n\t" "mov %0,%%dr2\n\t" "mov %1,%%dr7\n\t" : :"r" (zero),"r" (dr7)); -wrmsr (MSR_IA32_DEBUGCTLMSR ,0x1 );vmcs_write (GUEST_DR7 ,0x404 ); -vmcs_write (GUEST_DEBUGCTL ,0x2 );vmcs_write (ENT_CONTROLS ,vmcs_read (ENT_CONTROLS ) |ENT_LOAD_DBGCTLS );vmcs_write (EXI_CONTROLS ,vmcs_read (EXI_CONTROLS ) |EXI_SAVE_DBGCTLS );
@@ -1878,23 +1875,19 @@ static int dbgctls_init(struct vmcs *vmcs)return VMX_TEST_START ; } -static void dbgctls_main (void ) +static void dbgctls_dr7_main (void ) { -u64 dr7, debugctl; +u64 dr7; asmvolatile ("mov %%dr7,%0" :"=r" (dr7)); - debugctl =rdmsr (MSR_IA32_DEBUGCTLMSR ); -/* Commented out: KVM does not support DEBUGCTL so far */ - (void )debugctl; -report (dr7 ==0x404 ,"Load debug controls" /* && debugctl == 0x2 */ ); +report (dr7 ==0x404 ,"DR7: Load debug controls" ); dr7 =0x408 ; asmvolatile ("mov %0,%%dr7" : :"r" (dr7)); -wrmsr (MSR_IA32_DEBUGCTLMSR ,0x3 );vmx_set_test_stage (0 );vmcall (); -report (vmx_get_test_stage () ==1 ,"Save debug controls" ); +report (vmx_get_test_stage () ==1 ,"DR7: Save debug controls" );if (ctrl_enter_rev.set &ENT_LOAD_DBGCTLS || ctrl_exit_rev.set &EXI_SAVE_DBGCTLS ) {
@@ -1905,46 +1898,37 @@ static void dbgctls_main(void)vmcall (); asmvolatile ("mov %%dr7,%0" :"=r" (dr7)); - debugctl =rdmsr (MSR_IA32_DEBUGCTLMSR ); -/* Commented out: KVM does not support DEBUGCTL so far */ - (void )debugctl;report (dr7 ==0x402 , -"Guest=host debug controls" /* && debugctl == 0x1 */ ); +"DR7: Guest=host debug controls" ); dr7 =0x408 ; asmvolatile ("mov %0,%%dr7" : :"r" (dr7)); -wrmsr (MSR_IA32_DEBUGCTLMSR ,0x3 );vmx_set_test_stage (3 );vmcall (); -report (vmx_get_test_stage () ==4 ,"Don't save debug controls" ); +report (vmx_get_test_stage () ==4 ,"DR7: Don't save debug controls" ); } -static int dbgctls_exit_handler (union exit_reason exit_reason) +static int dbgctls_dr7_exit_handler (union exit_reason exit_reason) {u32 insn_len =vmcs_read (EXI_INST_LEN );u64 guest_rip =vmcs_read (GUEST_RIP ); -u64 dr7, debugctl; +u64 dr7; asmvolatile ("mov %%dr7,%0" :"=r" (dr7)); - debugctl =rdmsr (MSR_IA32_DEBUGCTLMSR );switch (exit_reason.basic) {case VMX_VMCALL :switch (vmx_get_test_stage ()) {case 0 : -if (dr7 ==0x400 && debugctl ==0 && -vmcs_read (GUEST_DR7 ) ==0x408 /* && -Commented out: KVM does not support DEBUGCTL so far -vmcs_read(GUEST_DEBUGCTL) == 0x3 */ ) +if (dr7 ==0x400 && +vmcs_read (GUEST_DR7 ) ==0x408 )vmx_inc_test_stage ();break ;case 2 : dr7 =0x402 ; asmvolatile ("mov %0,%%dr7" : :"r" (dr7)); -wrmsr (MSR_IA32_DEBUGCTLMSR ,0x1 );vmcs_write (GUEST_DR7 ,0x404 ); -vmcs_write (GUEST_DEBUGCTL ,0x2 );vmcs_write (ENT_CONTROLS ,vmcs_read (ENT_CONTROLS ) & ~ENT_LOAD_DBGCTLS );
@@ -1952,10 +1936,8 @@ static int dbgctls_exit_handler(union exit_reason exit_reason) vmcs_read(EXI_CONTROLS) & ~EXI_SAVE_DBGCTLS);break ;case 3 : -if (dr7 ==0x400 && debugctl ==0 && -vmcs_read (GUEST_DR7 ) ==0x404 /* && -Commented out: KVM does not support DEBUGCTL so far -vmcs_read(GUEST_DEBUGCTL) == 0x2 */ ) +if (dr7 ==0x400 && +vmcs_read (GUEST_DR7 ) ==0x404 )vmx_inc_test_stage ();break ; }
@@ -11780,7 +11762,7 @@ struct vmx_test vmx_tests[] = { interrupt_exit_handler, NULL, {0} }, {"nmi_hlt" , nmi_hlt_init, nmi_hlt_main, nmi_hlt_exit_handler, NULL, {0} }, - { "debug controls", dbgctls_init, dbgctls_main, dbgctls_exit_handler, + { "debug controls dr7", dbgctls_dr7_init, dbgctls_dr7_main, dbgctls_dr7_exit_handler, NULL, {0} }, { "MSR switch", msr_switch_init, msr_switch_main, msr_switch_exit_handler, NULL, {0}, msr_switch_entry_failure },
Signature · 1 line
2.43.5
Re: [kvm-unit-tests PATCH v2 1/4] nVMX: Remove the IA32_DEBUGCTLMSR access in debugctls test
Quoted 18 lines · Chenyi Qiang
"debug controls" test was added by commit
dc5c01f17b1a("VMX: Test behavior on set and cleared save/load debug controls") to verify that "VM-Entry load debug controls" and "VM-Exit save debug controls" are correctly emulated by KVM for nested VMX. But due to the limitation that KVM didn't supportMSR_IA32_DEBUGCTLfor guest at that time, the test commented out all the value comparison ofMSR_IA32_DEBUGCTLand leave it to future when KVM supports the MSR.The test doesn't check the functionality of save/restore guest
MSR_IA32_DEBUGCTLon vm-exit/entry, but it keeps the write ofMSR_IA32_DEBUGCTL. It leads tokvm_intel: kvm [18663]: vcpu0, guest rIP: 0x407de7 Unhandled WRMSR(0x1d9) = 0x1 kvm_intel: kvm [18663]: vcpu0, guest rIP: 0x0 Unhandled WRMSR(0x1d9) = 0x2 kvm_intel: kvm [18663]: vcpu0, guest rIP: 0x40936f Unhandled WRMSR(0x1d9) = 0x3 kvm_intel: kvm [18663]: vcpu0, guest rIP: 0x40cf09 Unhandled WRMSR(0x1d9) = 0x1 kvm_intel: kvm [18663]: vcpu0, guest rIP: 0x40940d Unhandled WRMSR(0x1d9) = 0x3
Quoted 4 lines
to the kernel log. Though it doesn't break the test, the log confuses people to think something wrong happened in the test case.
Current KVM doesn't support some bits of
MSR_IA32_DEBUGCTLbut they
This sentence doesn't read right because my version used "does support", not "doesn't support".
Quoted 146 lines
depend on the vcpu model exposed. To simplify the case and eliminate the confusing "Unhandled WRMSR(0x1d9)" log, remove the
MSR_IA32_DEBUGCTLlogic in the test and make it concentrate only on DR7. Following patch will bring backMSR_IA32_DEBUGCTLseparately.Reviewed-by Xiaoyao Li <[email protected]>Signed-off-by Chenyi Qiang <[email protected]>---
Changes in v2:
- Rewrite of commit message by Xiaoyao.
- Add RB from Xiaoyao.--- x86/vmx_tests.c | 46 ++++++++++++++-------------------------------- 1 file changed, 14 insertions(+), 32 deletions(-)x86/vmx_tests.c +14
-32@@ -1856,21 +1856,18 @@ static int nmi_hlt_exit_handler(union exit_reason exit_reason) } -static int dbgctls_init (struct vmcs *vmcs) +static int dbgctls_dr7_init (struct vmcs *vmcs) {u64 dr7 =0x402 ;u64 zero =0 ; -msr_bmp_init (); asmvolatile ("mov %0,%%dr0\n\t" "mov %0,%%dr1\n\t" "mov %0,%%dr2\n\t" "mov %1,%%dr7\n\t" : :"r" (zero),"r" (dr7)); -wrmsr (MSR_IA32_DEBUGCTLMSR ,0x1 );vmcs_write (GUEST_DR7 ,0x404 ); -vmcs_write (GUEST_DEBUGCTL ,0x2 );vmcs_write (ENT_CONTROLS ,vmcs_read (ENT_CONTROLS ) |ENT_LOAD_DBGCTLS );vmcs_write (EXI_CONTROLS ,vmcs_read (EXI_CONTROLS ) |EXI_SAVE_DBGCTLS );@@ -1878,23 +1875,19 @@ static int dbgctls_init(struct vmcs *vmcs)return VMX_TEST_START ; } -static void dbgctls_main (void ) +static void dbgctls_dr7_main (void ) { -u64 dr7, debugctl; +u64 dr7; asmvolatile ("mov %%dr7,%0" :"=r" (dr7)); - debugctl =rdmsr (MSR_IA32_DEBUGCTLMSR ); -/* Commented out: KVM does not support DEBUGCTL so far */ - (void )debugctl; -report (dr7 ==0x404 ,"Load debug controls" /* && debugctl == 0x2 */ ); +report (dr7 ==0x404 ,"DR7: Load debug controls" ); dr7 =0x408 ; asmvolatile ("mov %0,%%dr7" : :"r" (dr7)); -wrmsr (MSR_IA32_DEBUGCTLMSR ,0x3 );vmx_set_test_stage (0 );vmcall (); -report (vmx_get_test_stage () ==1 ,"Save debug controls" ); +report (vmx_get_test_stage () ==1 ,"DR7: Save debug controls" );if (ctrl_enter_rev.set &ENT_LOAD_DBGCTLS || ctrl_exit_rev.set &EXI_SAVE_DBGCTLS ) {@@ -1905,46 +1898,37 @@ static void dbgctls_main(void)vmcall (); asmvolatile ("mov %%dr7,%0" :"=r" (dr7)); - debugctl =rdmsr (MSR_IA32_DEBUGCTLMSR ); -/* Commented out: KVM does not support DEBUGCTL so far */ - (void )debugctl;report (dr7 ==0x402 , -"Guest=host debug controls" /* && debugctl == 0x1 */ ); +"DR7: Guest=host debug controls" ); dr7 =0x408 ; asmvolatile ("mov %0,%%dr7" : :"r" (dr7)); -wrmsr (MSR_IA32_DEBUGCTLMSR ,0x3 );vmx_set_test_stage (3 );vmcall (); -report (vmx_get_test_stage () ==4 ,"Don't save debug controls" ); +report (vmx_get_test_stage () ==4 ,"DR7: Don't save debug controls" ); } -static int dbgctls_exit_handler (union exit_reason exit_reason) +static int dbgctls_dr7_exit_handler (union exit_reason exit_reason) {u32 insn_len =vmcs_read (EXI_INST_LEN );u64 guest_rip =vmcs_read (GUEST_RIP ); -u64 dr7, debugctl; +u64 dr7; asmvolatile ("mov %%dr7,%0" :"=r" (dr7)); - debugctl =rdmsr (MSR_IA32_DEBUGCTLMSR );switch (exit_reason.basic) {case VMX_VMCALL :switch (vmx_get_test_stage ()) {case 0 : -if (dr7 ==0x400 && debugctl ==0 && -vmcs_read (GUEST_DR7 ) ==0x408 /* && -Commented out: KVM does not support DEBUGCTL so far -vmcs_read(GUEST_DEBUGCTL) == 0x3 */ ) +if (dr7 ==0x400 && +vmcs_read (GUEST_DR7 ) ==0x408 )vmx_inc_test_stage ();break ;case 2 : dr7 =0x402 ; asmvolatile ("mov %0,%%dr7" : :"r" (dr7)); -wrmsr (MSR_IA32_DEBUGCTLMSR ,0x1 );vmcs_write (GUEST_DR7 ,0x404 ); -vmcs_write (GUEST_DEBUGCTL ,0x2 );vmcs_write (ENT_CONTROLS ,vmcs_read (ENT_CONTROLS ) & ~ENT_LOAD_DBGCTLS );@@ -1952,10 +1936,8 @@ static int dbgctls_exit_handler(union exit_reason exit_reason) vmcs_read(EXI_CONTROLS) & ~EXI_SAVE_DBGCTLS);break ;case 3 : -if (dr7 ==0x400 && debugctl ==0 && -vmcs_read (GUEST_DR7 ) ==0x404 /* && -Commented out: KVM does not support DEBUGCTL so far -vmcs_read(GUEST_DEBUGCTL) == 0x2 */ ) +if (dr7 ==0x400 && +vmcs_read (GUEST_DR7 ) ==0x404 )vmx_inc_test_stage ();break ; }@@ -11780,7 +11762,7 @@ struct vmx_test vmx_tests[] = { interrupt_exit_handler, NULL, {0} }, {"nmi_hlt" , nmi_hlt_init, nmi_hlt_main, nmi_hlt_exit_handler, NULL, {0} }, - { "debug controls", dbgctls_init, dbgctls_main, dbgctls_exit_handler, + { "debug controls dr7", dbgctls_dr7_init, dbgctls_dr7_main, dbgctls_dr7_exit_handler, NULL, {0} }, { "MSR switch", msr_switch_init, msr_switch_main, msr_switch_exit_handler, NULL, {0}, msr_switch_entry_failure },
Re: [kvm-unit-tests PATCH v2 1/4] nVMX: Remove the IA32_DEBUGCTLMSR access in debugctls test
Quoted 19 lines · Xiaoyao Li
Quoted 18 lines · Chenyi Qiang
"debug controls" test was added by commit
dc5c01f17b1a("VMX: Test behavior on set and cleared save/load debug controls") to verify that "VM-Entry load debug controls" and "VM-Exit save debug controls" are correctly emulated by KVM for nested VMX. But due to the limitation that KVM didn't supportMSR_IA32_DEBUGCTLfor guest at that time, the test commented out all the value comparison ofMSR_IA32_DEBUGCTLand leave it to future when KVM supports the MSR.The test doesn't check the functionality of save/restore guest
MSR_IA32_DEBUGCTLon vm-exit/entry, but it keeps the write ofMSR_IA32_DEBUGCTL. It leads to
kvm_intel: kvm [18663]: vcpu0, guest rIP:0x407de7Unhandled WRMSR(0x1d9) =0x1
kvm_intel: kvm [18663]: vcpu0, guest rIP:0x0Unhandled WRMSR(0x1d9) =0x2
kvm_intel: kvm [18663]: vcpu0, guest rIP:0x40936fUnhandled WRMSR(0x1d9) =0x3
kvm_intel: kvm [18663]: vcpu0, guest rIP:0x40cf09Unhandled WRMSR(0x1d9) =0x1
kvm_intel: kvm [18663]: vcpu0, guest rIP:0x40940dUnhandled WRMSR(0x1d9) =0x3
Quoted 6 lines
Quoted 4 lines
to the kernel log. Though it doesn't break the test, the log confuses people to think something wrong happened in the test case.
Current KVM doesn't support some bits of
MSR_IA32_DEBUGCTLbut theyThis sentence doesn't read right because my version used "does support", not "doesn't support".
Oops, thanks for catching it.
PATCH v2 2/4 nVMX: Validate DEBUGCTLMSR_BUS_LOCK_DETECT states during VMX transitions
In reply to Chenyi QiangAdd tests to verify that DEBUGCTLMSR_BUS_LOCK_DETECT state is correctly handled during VMX transitions.
Wrap the VM-entry/VM-exit DEBUGCTL transition flow into a shared helper so follow-up DEBUGCTL feature tests can reuse the same checks.
The following behaviors are verified in the helper:
1. Guest states are loaded from VMCS iff "Load debug controls" VM-Entry control is set.
2. Guest states are saved to VMCS iff "Save debug controls" VM-Exit control is set.
3. DEBUGCTL MSR is cleared after VM exits.
--- lib/x86/msr.h | 1 + x86/unittests.cfg | 8 ++++ x86/vmx_tests.c | 96 +++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 105 insertions(+)
lib/x86/msr.h +1 -0
@@ -103,6 +103,7 @@/* DEBUGCTLMSR bits (others vary by model): */ #define DEBUGCTLMSR_LBR (1UL << 0)/* last branch recording */ #define DEBUGCTLMSR_BTF (1UL << 1)/* single-step on branches */ +#define DEBUGCTLMSR_BUS_LOCK_DETECT (1UL << 2)#define DEBUGCTLMSR_TR (1UL << 6)#define DEBUGCTLMSR_BTS (1UL << 7)#define DEBUGCTLMSR_BTINT (1UL << 8)
x86/unittests.cfg +8 -0
@@ -471,6 +471,14 @@ arch = x86_64 groups = vmx timeout = 240 +[vmx_bus_lock_detect_test] +file = vmx.flat +test_args = "vmx_bus_lock_detect_test" +qemu_params = -cpu max,+vmx +arch = x86_64 +groups = vmx +timeout = 240 + [debug] file = debug.flat arch = x86_64
x86/vmx_tests.c +96 -0
107 lines not on this page · raw message
Signature · 1 line
2.43.5
Re: [kvm-unit-tests PATCH v2 2/4] nVMX: Validate DEBUGCTLMSR_BUS_LOCK_DETECT states during VMX transitions
Quoted 6 lines · Chenyi Qiang
Add tests to verify that
DEBUGCTLMSR_BUS_LOCK_DETECTstate is correctly handled during VMX transitions.Wrap the VM-entry/VM-exit DEBUGCTL transition flow into a shared helper so follow-up DEBUGCTL feature tests can reuse the same checks.
Quoted 7 lines
The following behaviors are verified in the helper:
1. Guest states are loaded from VMCS iff "Load debug controls" VM-Entry control is set.
2. Guest states are saved to VMCS iff "Save debug controls" VM-Exit control is set.
3. DEBUGCTL MSR is cleared after VM exits.Signed-off-by Chenyi Qiang <[email protected]>
Though some nits below, the functionality looks good to me.
Quoted 117 lines
--- lib/x86/msr.h | 1 + x86/unittests.cfg | 8 ++++ x86/vmx_tests.c | 96 +++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 105 insertions(+)lib/x86/msr.h +1
-0@@ -103,6 +103,7 @@/* DEBUGCTLMSR bits (others vary by model): */ #define DEBUGCTLMSR_LBR (1UL << 0)/* last branch recording */ #define DEBUGCTLMSR_BTF (1UL << 1)/* single-step on branches */ +#define DEBUGCTLMSR_BUS_LOCK_DETECT (1UL << 2)#define DEBUGCTLMSR_TR (1UL << 6)#define DEBUGCTLMSR_BTS (1UL << 7)#define DEBUGCTLMSR_BTINT (1UL << 8)x86/unittests.cfg +8
-0@@ -471,6 +471,14 @@ arch = x86_64 groups = vmx timeout = 240 +[vmx_bus_lock_detect_test] +file = vmx.flat +test_args = "vmx_bus_lock_detect_test" +qemu_params = -cpu max,+vmx +arch = x86_64 +groups = vmx +timeout = 240 + [debug] file = debug.flat arch = x86_64x86/vmx_tests.c +72
-0@@ -11737,6 +11737,100 @@ static void vmx_cet_test(void)test_set_guest_finished (); } +static struct vmx_debugctl_test_data { +u64 mask; +u64 guest_debugctl; +} vmx_debugctl_test_data; + +static void vmx_debugctl_test_guest (void ) +{ + vmx_debugctl_test_data.guest_debugctl =rdmsr (MSR_IA32_DEBUGCTLMSR ); +vmcall (); + +wrmsr (MSR_IA32_DEBUGCTLMSR , vmx_debugctl_test_data.mask); +vmcall (); + + vmx_debugctl_test_data.guest_debugctl =rdmsr (MSR_IA32_DEBUGCTLMSR ); +vmcall (); + +wrmsr (MSR_IA32_DEBUGCTLMSR , vmx_debugctl_test_data.mask); +vmcall (); +} + +static void vmx_debugctl_transition_test (const char *label,u64 mask) +{ +u64 debugctl; + + vmx_debugctl_test_data.mask = mask; + +msr_bmp_init (); +wrmsr (MSR_IA32_DEBUGCTLMSR , mask); +vmcs_write (GUEST_DEBUGCTL ,0x0 ); + +/* Validate when save/load debug controls are set */ +vmcs_set_bits (ENT_CONTROLS ,ENT_LOAD_DBGCTLS ); +vmcs_set_bits (EXI_CONTROLS ,EXI_SAVE_DBGCTLS ); + +test_set_guest (vmx_debugctl_test_guest); + +enter_guest (); +skip_exit_vmcall (); +/* Validate VM-entry loads the guest DEBUGCTL value from GUEST_DEBUGCTL. */ +report (vmx_debugctl_test_data.guest_debugctl ==0x0 , +"%s: Load debug controls" , label); + +enter_guest (); +skip_exit_vmcall (); + debugctl =rdmsr (MSR_IA32_DEBUGCTLMSR ); +/* Validate VM-exit clears host DEBUGCTL and saves guest DEBUGCTL into the VMCS. */ +report (debugctl ==0x0 &&vmcs_read (GUEST_DEBUGCTL ) == mask, +"%s: Save debug controls" , label); + +if (ctrl_enter_rev.set &ENT_LOAD_DBGCTLS || + ctrl_exit_rev.set &EXI_SAVE_DBGCTLS ) { +printf ("\tDebug controls are always loaded/saved\n" ); +test_set_guest_finished (); +return ; + } + +wrmsr (MSR_IA32_DEBUGCTLMSR , mask); +vmcs_write (GUEST_DEBUGCTL ,0x0 ); +/* Validate when save/load debug controls are clear */ +vmcs_clear_bits (ENT_CONTROLS ,ENT_LOAD_DBGCTLS ); +vmcs_clear_bits (EXI_CONTROLS ,EXI_SAVE_DBGCTLS ); + +enter_guest (); +skip_exit_vmcall (); +/* Validate guest observes the host's DEBUGCTL value. */ +report (vmx_debugctl_test_data.guest_debugctl == mask, +"%s: Guest=host debug controls" , label); + +wrmsr (MSR_IA32_DEBUGCTLMSR ,0x0 ); +vmcs_write (GUEST_DEBUGCTL ,0x0 ); + +enter_guest ();
x86/vmx_tests.c static void vmx_cet_test(void) · line 11821
Quoted 10 lines
x86/vmx_tests.c +10
-0+skip_exit_vmcall (); + debugctl =rdmsr (MSR_IA32_DEBUGCTLMSR ); +/* Validate VM-exit clears host DEBUGCTL and does not save guest DEBUGCTL into the VMCS. */ +report (debugctl ==0x0 &&vmcs_read (GUEST_DEBUGCTL ) ==0x0 , +"%s: Don't save debug controls" , label); + +enter_guest (); +} + +static void vmx_bus_lock_detect_test (void )
the name reads ambiguous to me.
how about debug_controls_debugctrlmsr_bus_lock_detect_test? hmm, seems too lengthy
x86/vmx_tests.c static void vmx_cet_test(void) · line 11823
Quoted 2 lines
x86/vmx_tests.c +2
-0+{ +
unnecessary new line.
Quoted 21 lines
x86/vmx_tests.c +12
-0+if (!this_cpu_has (X86_FEATURE_BUS_LOCK_DETECT )) { +report_skip ("%s : \"Bus Lock Detect\" not supported" , __func__); +return ; + } + +vmx_debugctl_transition_test ("DEBUGCTLMSR.BUS_LOCK_DETECT" , +DEBUGCTLMSR_BUS_LOCK_DETECT ); +report_pass (__func__); +} +#define TEST (name) { #name, .v2 = name }/* name/init/guest_main/exit_handler/syscall_handler/guest_regs */ @@ -11858,5 +11952,7 @@ struct vmx_test vmx_tests[] = {TEST (vmx_canonical_test),/* "Load CET" VM-entry/exit controls tests. */ TEST (vmx_cet_test), +/* "debug controls VM-entry/exit controls tests" for DEBUGCTLMSR_BUS_LOCK_DETECT */ +TEST (vmx_bus_lock_detect_test), { NULL, NULL, NULL, NULL, NULL, {0} }, };
Re: [kvm-unit-tests PATCH v2 2/4] nVMX: Validate DEBUGCTLMSR_BUS_LOCK_DETECT states during VMX transitions
Quoted 147 lines · Xiaoyao Li
Quoted 6 lines · Chenyi Qiang
Add tests to verify that
DEBUGCTLMSR_BUS_LOCK_DETECTstate is correctly handled during VMX transitions.Wrap the VM-entry/VM-exit DEBUGCTL transition flow into a shared helper so follow-up DEBUGCTL feature tests can reuse the same checks.
Quoted 7 lines
The following behaviors are verified in the helper:
1. Guest states are loaded from VMCS iff "Load debug controls" VM-Entry control is set.
2. Guest states are saved to VMCS iff "Save debug controls" VM-Exit control is set.
3. DEBUGCTL MSR is cleared after VM exits.Signed-off-by Chenyi Qiang <[email protected]>Though some nits below, the functionality looks good to me.
Reviewed-by Xiaoyao Li <[email protected]>Quoted 115 lines
---
lib/x86/msr.h | 1 +
x86/unittests.cfg | 8 ++++
x86/vmx_tests.c | 96 +++++++++++++++++++++++++++++++++++++++++++++++3 files changed, 105 insertions(+)lib/x86/msr.h +1
-0@@ -103,6 +103,7 @@ /* DEBUGCTLMSR bits (others vary by model): */ #define DEBUGCTLMSR_LBR (1UL << 0) /* last branch recording */ #define DEBUGCTLMSR_BTF (1UL << 1) /* single-step on branches */ +#define DEBUGCTLMSR_BUS_LOCK_DETECT (1UL << 2) #define DEBUGCTLMSR_TR (1UL << 6) #define DEBUGCTLMSR_BTS (1UL << 7) #define DEBUGCTLMSR_BTINT (1UL << 8)x86/unittests.cfg +0
-0@@ -471,6 +471,14 @@ arch = x86_64groups = vmx
timeout = 240
+[vmx_bus_lock_detect_test]x86/unittests.cfg +7
-0+file = vmx.flat +test_args = "vmx_bus_lock_detect_test" +qemu_params = -cpu max,+vmx +arch = x86_64 +groups = vmx +timeout = 240 +[debug]
file = debug.flat
arch =x86_64x86/vmx_tests.c +71
-0@@ -11737,6 +11737,100 @@ static void vmx_cet_test(void) test_set_guest_finished(); } +static struct vmx_debugctl_test_data { + u64 mask; + u64 guest_debugctl; +} vmx_debugctl_test_data; + +static void vmx_debugctl_test_guest (void ) +{ + vmx_debugctl_test_data.guest_debugctl = rdmsr(MSR_IA32_DEBUGCTLMSR); + vmcall(); + + wrmsr(MSR_IA32_DEBUGCTLMSR, vmx_debugctl_test_data.mask); + vmcall(); + + vmx_debugctl_test_data.guest_debugctl = rdmsr(MSR_IA32_DEBUGCTLMSR); + vmcall(); + + wrmsr(MSR_IA32_DEBUGCTLMSR, vmx_debugctl_test_data.mask); + vmcall(); +} + +static void vmx_debugctl_transition_test (const char *label,u64 mask) +{ + u64 debugctl; + + vmx_debugctl_test_data.mask = mask; + + msr_bmp_init(); + wrmsr(MSR_IA32_DEBUGCTLMSR, mask); + vmcs_write(GUEST_DEBUGCTL, 0x0); + + /* Validate when save/load debug controls are set */ + vmcs_set_bits(ENT_CONTROLS, ENT_LOAD_DBGCTLS); + vmcs_set_bits(EXI_CONTROLS, EXI_SAVE_DBGCTLS); + + test_set_guest(vmx_debugctl_test_guest); + + enter_guest(); + skip_exit_vmcall(); + /* Validate VM-entry loads the guest DEBUGCTL value from GUEST_DEBUGCTL. */ + report(vmx_debugctl_test_data.guest_debugctl == 0x0, + "%s: Load debug controls", label); + + enter_guest(); + skip_exit_vmcall(); + debugctl = rdmsr(MSR_IA32_DEBUGCTLMSR); + /* Validate VM-exit clears host DEBUGCTL and saves guest DEBUGCTL into the VMCS. */ + report(debugctl == 0x0 && vmcs_read(GUEST_DEBUGCTL) == mask, + "%s: Save debug controls", label); + + if (ctrl_enter_rev.set & ENT_LOAD_DBGCTLS || + ctrl_exit_rev.set & EXI_SAVE_DBGCTLS) { + printf("\tDebug controls are always loaded/saved\n"); + test_set_guest_finished(); + return; + } + + wrmsr(MSR_IA32_DEBUGCTLMSR, mask); + vmcs_write(GUEST_DEBUGCTL, 0x0); + /* Validate when save/load debug controls are clear */ + vmcs_clear_bits(ENT_CONTROLS, ENT_LOAD_DBGCTLS); + vmcs_clear_bits(EXI_CONTROLS, EXI_SAVE_DBGCTLS); + + enter_guest(); + skip_exit_vmcall(); + /* Validate guest observes the host's DEBUGCTL value. */ + report(vmx_debugctl_test_data.guest_debugctl == mask, + "%s: Guest=host debug controls", label); + + wrmsr(MSR_IA32_DEBUGCTLMSR, 0x0); + vmcs_write(GUEST_DEBUGCTL, 0x0); + + enter_guest();x86/vmx_tests.c static void vmx_cet_test(void) · line 11820
Quoted 10 lines
x86/vmx_tests.c +10
-0+ skip_exit_vmcall(); + debugctl = rdmsr(MSR_IA32_DEBUGCTLMSR); + /* Validate VM-exit clears host DEBUGCTL and does not save guest DEBUGCTL into the VMCS. */ + report(debugctl == 0x0 && vmcs_read(GUEST_DEBUGCTL) == 0x0, + "%s: Don't save debug controls", label); + + enter_guest(); +} + +static void vmx_bus_lock_detect_test (void )the name reads ambiguous to me.
Quoted 1 line
how about
debug_controls_debugctrlmsr_bus_lock_detect_test? hmm, seems too lengthy
I'm also hesitant about what kind of function name to use and whether it needs to be specific to the debug controls.
Sean's suggestion was to "add dedicated tests (for BUS_LOCK_DETECT and LBR), and get any coverage for KVM's handling of DEBUGCTL reads and writes as a side effect."
That makes me think the case should focus on the feature, with DEBUGCTL handling as a subcase for that feature. Perhaps I'm overthinking this a bit.
Quoted 5 lines
x86/vmx_tests.c static void vmx_cet_test(void) · line 11822
Quoted 3 lines
x86/vmx_tests.c +2
-0+{ +unnecessary new line.
Fixed, thanks!
Sean Christopherson
reviewerRe: [kvm-unit-tests PATCH v2 2/4] nVMX: Validate DEBUGCTLMSR_BUS_LOCK_DETECT states during VMX transitions
Quoted 16 lines · Chenyi Qiang
Quoted 15 lines · Xiaoyao Li
Quoted 8 lines · Chenyi Qiang
x86/unittests.cfg +0
-0@@ -471,6 +471,14 @@ arch = x86_64groups = vmx
timeout = 240
+[vmx_bus_lock_detect_test]x86/unittests.cfg
Quoted 6 lines
x86/unittests.cfg +6
-0+file = vmx.flat +test_args = "vmx_bus_lock_detect_test" +qemu_params = -cpu max,+vmx +arch = x86_64 +groups = vmx +timeout = 240
Why does this need a separate config, and with a massive timeout? This should be nearly instantaneous, no?
Ugh, because you copy+pasted vmx_cet. That thing doesn't need to exist, the testcase is run by the common "vmx" entry. I'll send a patch to drop vmx_cet.
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
+
[debug]
file = debug.flat
arch =x86_64x86/vmx_tests.c +0
-0
Quoted 8 lines
Quoted 8 lines
x86/vmx_tests.c static void vmx_cet_test(void) · line 11740
Quoted 8 lines
index
91f417c6..a3e52d3b100644x86/vmx_tests.c +1
-0@@ -11737,6 +11737,100 @@ static void vmx_cet_test(void) test_set_guest_finished(); } +static struct vmx_debugctl_test_data { + u64 mask;
It's not a mask, it's an explicit value.
Quoted 2 lines
Quoted 2 lines
x86/vmx_tests.c static void vmx_cet_test(void) · line 11742
Quoted 2 lines
x86/vmx_tests.c +2
-0+ u64 guest_debugctl; +} vmx_debugctl_test_data;
There's no need for a struct, only a single u64 is needed to pass information back and forth since there's a VMCALL after every step.
Quoted 46 lines
Quoted 46 lines
Quoted 46 lines
x86/vmx_tests.c +46
-0+static void vmx_debugctl_test_guest (void ) +{ + vmx_debugctl_test_data.guest_debugctl = rdmsr(MSR_IA32_DEBUGCTLMSR); + vmcall(); + + wrmsr(MSR_IA32_DEBUGCTLMSR, vmx_debugctl_test_data.mask); + vmcall(); + + vmx_debugctl_test_data.guest_debugctl = rdmsr(MSR_IA32_DEBUGCTLMSR); + vmcall(); + + wrmsr(MSR_IA32_DEBUGCTLMSR, vmx_debugctl_test_data.mask); + vmcall(); +} + +static void vmx_debugctl_transition_test (const char *label,u64 mask) +{ + u64 debugctl; + + vmx_debugctl_test_data.mask = mask; + + msr_bmp_init(); + wrmsr(MSR_IA32_DEBUGCTLMSR, mask); + vmcs_write(GUEST_DEBUGCTL, 0x0); + + /* Validate when save/load debug controls are set */ + vmcs_set_bits(ENT_CONTROLS, ENT_LOAD_DBGCTLS); + vmcs_set_bits(EXI_CONTROLS, EXI_SAVE_DBGCTLS); + + test_set_guest(vmx_debugctl_test_guest); + + enter_guest(); + skip_exit_vmcall(); + /* Validate VM-entry loads the guest DEBUGCTL value from GUEST_DEBUGCTL. */ + report(vmx_debugctl_test_data.guest_debugctl == 0x0, + "%s: Load debug controls", label); + + enter_guest(); + skip_exit_vmcall(); + debugctl = rdmsr(MSR_IA32_DEBUGCTLMSR); + /* Validate VM-exit clears host DEBUGCTL and saves guest DEBUGCTL into the VMCS. */ + report(debugctl == 0x0 && vmcs_read(GUEST_DEBUGCTL) == mask, + "%s: Save debug controls", label); + + if (ctrl_enter_rev.set & ENT_LOAD_DBGCTLS || + ctrl_exit_rev.set & EXI_SAVE_DBGCTLS) {
Quoted 8 lines
Quoted 8 lines
x86/vmx_tests.c static void vmx_cet_test(void) · line 11796
Quoted 8 lines
x86/vmx_tests.c +8
-0+ printf("\tDebug controls are always loaded/saved\n"); + test_set_guest_finished(); + return; + } + + wrmsr(MSR_IA32_DEBUGCTLMSR, mask); + vmcs_write(GUEST_DEBUGCTL, 0x0); + /* Validate when save/load debug controls are clear */
We should also test with only of the controls set.
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
x86/vmx_tests.c +8
-0+ vmcs_clear_bits(ENT_CONTROLS, ENT_LOAD_DBGCTLS); + vmcs_clear_bits(EXI_CONTROLS, EXI_SAVE_DBGCTLS); + + enter_guest(); + skip_exit_vmcall(); + /* Validate guest observes the host's DEBUGCTL value. */ + report(vmx_debugctl_test_data.guest_debugctl == mask, + "%s: Guest=host debug controls", label);
Quoted 8 lines
Quoted 8 lines
x86/vmx_tests.c static void vmx_cet_test(void) · line 11812
Quoted 8 lines
x86/vmx_tests.c +8
-0+ + wrmsr(MSR_IA32_DEBUGCTLMSR, 0x0); + vmcs_write(GUEST_DEBUGCTL, 0x0); + + enter_guest(); + skip_exit_vmcall(); + debugctl = rdmsr(MSR_IA32_DEBUGCTLMSR); + /* Validate VM-exit clears host DEBUGCTL and does not save guest DEBUGCTL into the VMCS. */
This can/should be done on *every* VM-Exit, using report_fail() to avoid polluting the PASS results with a relatively uninteresting testcase.
Quoted 9 lines
Quoted 9 lines
x86/vmx_tests.c static void vmx_cet_test(void) · line 11819
Quoted 7 lines
x86/vmx_tests.c +7
-0+ report(debugctl == 0x0 && vmcs_read(GUEST_DEBUGCTL) == 0x0, + "%s: Don't save debug controls", label); + + enter_guest(); +} + +static void vmx_bus_lock_detect_test (void )the name reads ambiguous to me.
The name would be great, _if_ the test were actually testing BUS_LOCK_DETECT, i.e. needs to actually generate a bus lock in L2 and verify L1 gets the VM-Exit. That's what I was suggesting in my earlier feedback: actually test BUS_LOCK_DETECT, and verify vmcs.GUEST_DEBUGCTL handling as a side effect.
But since you've already gone thorugh most of the effort... :-)
Rather than split this into three tests, bundle it all into one test. Splitting makes sense _if_ the guest is actually validating functionality, but if the goal is purely to validate the values and not the semantics, then bundling is much more interesting as it allows testing combinations.
And since only three bits are set, just validate all combinations, for both the host and the guest. It's a total of 8 values, so at most 64 total testcases to cover both host and guest.
This works for me, I'll post a v3.
--- lib/x86/msr.h | 2 + x86/vmx_tests.c | 150 ++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 152 insertions(+)
lib/x86/msr.h +2 -0
@@ -103,12 +103,14 @@/* DEBUGCTLMSR bits (others vary by model): */ #define DEBUGCTLMSR_LBR (1UL << 0)/* last branch recording */ #define DEBUGCTLMSR_BTF (1UL << 1)/* single-step on branches */ +#define DEBUGCTLMSR_BUS_LOCK_DETECT (1UL << 2)#define DEBUGCTLMSR_TR (1UL << 6)#define DEBUGCTLMSR_BTS (1UL << 7)#define DEBUGCTLMSR_BTINT (1UL << 8)#define DEBUGCTLMSR_BTS_OFF_OS (1UL << 9)#define DEBUGCTLMSR_BTS_OFF_USR (1UL << 10)#define DEBUGCTLMSR_FREEZE_LBRS_ON_PMI (1UL << 11) +#define DEBUGCTLMSR_RTM_DEBUG (1UL << 15)#define MSR_LBR_NHM_FROM 0x00000680#define MSR_LBR_NHM_TO 0x000006c0
x86/vmx_tests.c +150 -0
161 lines not on this page · raw message
base-commit: da6e732372e64a31010b0c8cbfc550a9d83195ba
Re: [kvm-unit-tests PATCH v2 2/4] nVMX: Validate DEBUGCTLMSR_BUS_LOCK_DETECT states during VMX transitions
Quoted 21 lines · Sean Christopherson
Quoted 16 lines · Chenyi Qiang
Quoted 15 lines · Xiaoyao Li
Quoted 5 lines · Chenyi Qiang
x86/unittests.cfg +0
-0x86/unittests.cfg arch = x86_64 · line 479
Quoted 9 lines
x86/unittests.cfg +6
-0@@ -471,6 +471,14 @@ arch = x86_64 groups = vmx timeout = 240 +[vmx_bus_lock_detect_test] +file = vmx.flat +test_args = "vmx_bus_lock_detect_test" +qemu_params = -cpu max,+vmx +arch = x86_64 +groups = vmx +timeout = 240Why does this need a separate config, and with a massive timeout? This should be nearly instantaneous, no?
Quoted 2 lines
Ugh, because you copy+pasted
vmx_cet. That thing doesn't need to exist, the testcase is run by the common "vmx" entry. I'll send a patch to dropvmx_cet.
I told Chenyi that to actually be able to test LBR bit, we might need some specific QEMU configuration to enable PMU and legacy LBR and it will need a specific config.
I missed that he even added the config for BUS_LOCK_DETECT and RTM tests.
Sean Christopherson
reviewerRe: [kvm-unit-tests PATCH v2 2/4] nVMX: Validate DEBUGCTLMSR_BUS_LOCK_DETECT states during VMX transitions
Quoted 22 lines · Xiaoyao Li
Quoted 21 lines · Sean Christopherson
Quoted 16 lines · Chenyi Qiang
Quoted 15 lines · Xiaoyao Li
Quoted 5 lines · Chenyi Qiang
x86/unittests.cfg +0
-0x86/unittests.cfg arch = x86_64 · line 479
Quoted 9 lines
x86/unittests.cfg +6
-0@@ -471,6 +471,14 @@ arch = x86_64 groups = vmx timeout = 240 +[vmx_bus_lock_detect_test] +file = vmx.flat +test_args = "vmx_bus_lock_detect_test" +qemu_params = -cpu max,+vmx +arch = x86_64 +groups = vmx +timeout = 240Why does this need a separate config, and with a massive timeout? This should be nearly instantaneous, no?
Quoted 6 lines
Quoted 2 lines
Ugh, because you copy+pasted
vmx_cet. That thing doesn't need to exist, the testcase is run by the common "vmx" entry. I'll send a patch to dropvmx_cet.I told Chenyi that to actually be able to test LBR bit, we might need some specific QEMU configuration to enable PMU and legacy LBR and it will need a specific config.
Ah. AFAICT, it's just the migratable=no thing? If so, any reason we can't do that for the main "vmx" testcase?
unittests.cfg +1 -1
@@ -320,7 +320,7 @@ qemu_params = -cpu max,host-phys-bits [vmx] file = vmx.flat test_args = "-exit_monitor_from_l2_test -ept_access* -vmx_smp* -vmx_vmcs_shadow_test -atomic_switch_overflow_msrs_test -vmx_init_signal_test -vmx_apic_passthrough_tpr_threshold_test -apic_reg_virt_test -virt_x2apic_mode_test -vmx_pf_exception_test -vmx_pf_exception_forced_emulation_test -vmx_pf_no_vpid_test -vmx_pf_invvpid_test -vmx_pf_vpid_test -vmx_basic_vid_test -vmx_eoi_virt_test -vmx_posted_interrupts_test" -qemu_params = -cpu max,+vmx +qemu_params = -cpu max,migratable=no,+vmx arch = x86_64 groups = vmx
PATCH v2 3/4 nVMX: Validate DEBUGCTLMSR_RTM_DEBUG states during VMX transitions
In reply to Chenyi QiangAdd tests to verify that DEBUGCTLMSR_RTM_DEBUG state is correctly handled during VMX transitions on top of the shared helper.
--- lib/x86/msr.h | 1 + x86/unittests.cfg | 8 ++++++++ x86/vmx_tests.c | 14 ++++++++++++++ 3 files changed, 23 insertions(+)
lib/x86/msr.h +1 -0
@@ -110,6 +110,7 @@#define DEBUGCTLMSR_BTS_OFF_OS (1UL << 9)#define DEBUGCTLMSR_BTS_OFF_USR (1UL << 10)#define DEBUGCTLMSR_FREEZE_LBRS_ON_PMI (1UL << 11) +#define DEBUGCTLMSR_RTM_DEBUG (1UL << 15)#define MSR_LBR_NHM_FROM 0x00000680#define MSR_LBR_NHM_TO 0x000006c0
x86/unittests.cfg +8 -0
@@ -479,6 +479,14 @@ arch = x86_64 groups = vmx timeout = 240 +[vmx_rtm_test] +file = vmx.flat +test_args = "vmx_rtm_test" +qemu_params = -cpu max,+vmx +arch = x86_64 +groups = vmx +timeout = 240 + [debug] file = debug.flat arch = x86_64
x86/vmx_tests.c +14 -0
@@ -11831,6 +11831,18 @@ static void vmx_bus_lock_detect_test(void)report_pass (__func__); } +static void vmx_rtm_test (void ) +{ +if (!this_cpu_has (X86_FEATURE_RTM )) { +report_skip ("%s : \"RTM\" not supported" , __func__); +return ; + } + +vmx_debugctl_transition_test ("DEBUGCTLMSR.RTM_DEBUG" , +DEBUGCTLMSR_RTM_DEBUG ); +report_pass (__func__); +} +#define TEST (name) { #name, .v2 = name }/* name/init/guest_main/exit_handler/syscall_handler/guest_regs */
@@ -11954,5 +11966,7 @@ struct vmx_test vmx_tests[] = {TEST (vmx_cet_test),/* "debug controls VM-entry/exit controls tests" for DEBUGCTLMSR_BUS_LOCK_DETECT */ TEST (vmx_bus_lock_detect_test), +/* "debug controls VM-entry/exit controls tests" for DEBUGCTLMSR_RTM_DEBUG */ +TEST (vmx_rtm_test), { NULL, NULL, NULL, NULL, NULL, {0} }, };
Signature · 1 line
2.43.5
Re: [kvm-unit-tests PATCH v2 3/4] nVMX: Validate DEBUGCTLMSR_RTM_DEBUG states during VMX transitions
Quoted 46 lines · Chenyi Qiang
Add tests to verify that
DEBUGCTLMSR_RTM_DEBUGstate is correctly handled during VMX transitions on top of the shared helper.Signed-off-by Chenyi Qiang <[email protected]>--- lib/x86/msr.h | 1 + x86/unittests.cfg | 8 ++++++++ x86/vmx_tests.c | 14 ++++++++++++++ 3 files changed, 23 insertions(+)lib/x86/msr.h +1
-0@@ -110,6 +110,7 @@#define DEBUGCTLMSR_BTS_OFF_OS (1UL << 9)#define DEBUGCTLMSR_BTS_OFF_USR (1UL << 10)#define DEBUGCTLMSR_FREEZE_LBRS_ON_PMI (1UL << 11) +#define DEBUGCTLMSR_RTM_DEBUG (1UL << 15)#define MSR_LBR_NHM_FROM 0x00000680#define MSR_LBR_NHM_TO 0x000006c0x86/unittests.cfg +8
-0@@ -479,6 +479,14 @@ arch = x86_64 groups = vmx timeout = 240 +[vmx_rtm_test] +file = vmx.flat +test_args = "vmx_rtm_test" +qemu_params = -cpu max,+vmx +arch = x86_64 +groups = vmx +timeout = 240 + [debug] file = debug.flat arch = x86_64x86/vmx_tests.c +0
-0
x86/vmx_tests.c static void vmx_bus_lock_detect_test(void) · line 11834
Quoted 4 lines
x86/vmx_tests.c +1
-0@@ -11831,6 +11831,18 @@ static void vmx_bus_lock_detect_test(void)report_pass (__func__); } +static void vmx_rtm_test (void )
still the name is not perfect to me, otherwise
Quoted 22 lines
x86/vmx_tests.c +13
-0+{ +if (!this_cpu_has (X86_FEATURE_RTM )) { +report_skip ("%s : \"RTM\" not supported" , __func__); +return ; + } + +vmx_debugctl_transition_test ("DEBUGCTLMSR.RTM_DEBUG" , +DEBUGCTLMSR_RTM_DEBUG ); +report_pass (__func__); +} +#define TEST (name) { #name, .v2 = name }/* name/init/guest_main/exit_handler/syscall_handler/guest_regs */ @@ -11954,5 +11966,7 @@ struct vmx_test vmx_tests[] = {TEST (vmx_cet_test),/* "debug controls VM-entry/exit controls tests" for DEBUGCTLMSR_BUS_LOCK_DETECT */ TEST (vmx_bus_lock_detect_test), +/* "debug controls VM-entry/exit controls tests" for DEBUGCTLMSR_RTM_DEBUG */ +TEST (vmx_rtm_test), { NULL, NULL, NULL, NULL, NULL, {0} }, };
PATCH v2 4/4 nVMX: Validate DEBUGCTLMSR_LBR states during VMX transitions
In reply to Chenyi QiangAdd tests to verify that DEBUGCTLMSR_LBR state is correctly handled during VMX transitions on top of the shared helper.
--- x86/unittests.cfg | 9 +++++++++ x86/vmx_tests.c | 19 +++++++++++++++++++ 2 files changed, 28 insertions(+)
x86/unittests.cfg +9 -0
@@ -487,6 +487,15 @@ arch = x86_64 groups = vmx timeout = 240 +[vmx_legacy_lbr_test] +file = vmx.flat +test_args = "vmx_legacy_lbr_test" +qemu_params = -cpu host,migratable=no,+vmx +check = /sys/module/kvm/parameters/enable_pmu=Y /sys/module/kvm/parameters/ignore_msrs=N +arch = x86_64 +groups = vmx +timeout = 240 + [debug] file = debug.flat arch = x86_64
x86/vmx_tests.c +19 -0
@@ -11843,6 +11843,23 @@ static void vmx_rtm_test(void)report_pass (__func__); } +static void vmx_legacy_lbr_test (void ) +{ +if (!this_cpu_has (X86_FEATURE_PDCM )) { +report_skip ("%s : Perfmon/Debug Capabilities MSR not supported" , + __func__); +return ; + } + +if (!pmu_lbr_version ()) { +report_skip ("%s : LBR not supported" , __func__); +return ; + } + +vmx_debugctl_transition_test ("DEBUGCTLMSR.LBR" ,DEBUGCTLMSR_LBR ); +report_pass (__func__); +} +#define TEST (name) { #name, .v2 = name }/* name/init/guest_main/exit_handler/syscall_handler/guest_regs */
@@ -11968,5 +11985,7 @@ struct vmx_test vmx_tests[] = {TEST (vmx_bus_lock_detect_test),/* "debug controls VM-entry/exit controls tests" for DEBUGCTLMSR_RTM_DEBUG */ TEST (vmx_rtm_test), +/* "debug controls VM-entry/exit controls tests" for DEBUGCTLMSR_LBR */ +TEST (vmx_legacy_lbr_test), { NULL, NULL, NULL, NULL, NULL, {0} }, };
Signature · 1 line
2.43.5
Re: [kvm-unit-tests PATCH v2 4/4] nVMX: Validate DEBUGCTLMSR_LBR states during VMX transitions
Quoted 14 lines · Chenyi Qiang
Add tests to verify that
DEBUGCTLMSR_LBRstate is correctly handled during VMX transitions on top of the shared helper.Signed-off-by Chenyi Qiang <[email protected]>--- x86/unittests.cfg | 9 +++++++++ x86/vmx_tests.c | 19 +++++++++++++++++++ 2 files changed, 28 insertions(+)x86/unittests.cfg +0
-0
x86/unittests.cfg arch = x86_64 · line 494
Quoted 8 lines
x86/unittests.cfg +5
-0@@ -487,6 +487,15 @@ arch = x86_64 groups = vmx timeout = 240 +[vmx_legacy_lbr_test] +file = vmx.flat +test_args = "vmx_legacy_lbr_test" +qemu_params = -cpu host,migratable=no,+vmx +check = /sys/module/kvm/parameters/enable_pmu=Y /sys/module/kvm/parameters/ignore_msrs=N
What's the purpose of checking ignore_msrs here? can you elaborate a bit?
Quoted 43 lines
x86/unittests.cfg +4
-0+arch = x86_64 +groups = vmx +timeout = 240 + [debug] file = debug.flat arch = x86_64x86/vmx_tests.c +19
-0@@ -11843,6 +11843,23 @@ static void vmx_rtm_test(void)report_pass (__func__); } +static void vmx_legacy_lbr_test (void ) +{ +if (!this_cpu_has (X86_FEATURE_PDCM )) { +report_skip ("%s : Perfmon/Debug Capabilities MSR not supported" , + __func__); +return ; + } + +if (!pmu_lbr_version ()) { +report_skip ("%s : LBR not supported" , __func__); +return ; + } + +vmx_debugctl_transition_test ("DEBUGCTLMSR.LBR" ,DEBUGCTLMSR_LBR ); +report_pass (__func__); +} +#define TEST (name) { #name, .v2 = name }/* name/init/guest_main/exit_handler/syscall_handler/guest_regs */ @@ -11968,5 +11985,7 @@ struct vmx_test vmx_tests[] = {TEST (vmx_bus_lock_detect_test),/* "debug controls VM-entry/exit controls tests" for DEBUGCTLMSR_RTM_DEBUG */ TEST (vmx_rtm_test), +/* "debug controls VM-entry/exit controls tests" for DEBUGCTLMSR_LBR */ +TEST (vmx_legacy_lbr_test), { NULL, NULL, NULL, NULL, NULL, {0} }, };
Re: [kvm-unit-tests PATCH v2 4/4] nVMX: Validate DEBUGCTLMSR_LBR states during VMX transitions
Quoted 10 lines · Xiaoyao Li
Quoted 9 lines · Chenyi Qiang
Add tests to verify that
DEBUGCTLMSR_LBRstate is correctly handled during VMX transitions on top of the shared helper.Signed-off-by Chenyi Qiang <[email protected]>---
x86/unittests.cfg | 9 +++++++++
x86/vmx_tests.c | 19 +++++++++++++++++++2 files changed, 28 insertions(+)
Quoted 14 lines
x86/unittests.cfg arch = x86_64 · line 494
Quoted 12 lines
x86/unittests.cfg +0
-0@@ -487,6 +487,15 @@ arch = x86_64groups = vmx
timeout = 240
+[vmx_legacy_lbr_test]x86/unittests.cfg +4
-0+file = vmx.flat +test_args = "vmx_legacy_lbr_test" +qemu_params = -cpu host,migratable=no,+vmx +check = /sys/module/kvm/parameters/enable_pmu=Y /sys/module/kvm/parameters/ignore_msrs=NWhat's the purpose of checking
ignore_msrshere? can you elaborate a bit?
This check is mentioned in pmu_lbr, and I followed it without giving it much thought at the time. After reconsideration, this check is not needed in our case. The pmu_lbr requires it to ensure that accessing model-unsupported LBR MSRs generates a #GP, but DEBUGCTLMSR does not need it. Will drop it in next version.