On Tue, Apr 04, 2023, Sean Christopherson wrote: > Add a forced emulation variant of vmx_pf_exception_test to exercise KVM > emulation of L2 instructions and accesses. Like the non-nested version, > make the test nodefault as forcing KVM to emulate drastically increases > the runtime. > > Signed-off-by: Sean Christopherson <seanjc@xxxxxxxxxx> > --- > x86/unittests.cfg | 6 ++++++ > x86/vmx_tests.c | 25 ++++++++++++++++++++----- > 2 files changed, 26 insertions(+), 5 deletions(-) > > diff --git a/x86/unittests.cfg b/x86/unittests.cfg > index c878363e..0971bb3f 100644 > --- a/x86/unittests.cfg > +++ b/x86/unittests.cfg > @@ -409,6 +409,12 @@ extra_params = -cpu max,+vmx -append "vmx_pf_exception_test" > arch = x86_64 > groups = vmx nested_exception > > +[vmx_pf_exception_test_fep] > +file = vmx.flat > +extra_params = -cpu max,+vmx -append "vmx_pf_exception_forced_emulation_test" > +arch = x86_64 > +groups = vmx nested_exception nodefault And I forgot how the nVMX "test" works. vmx_pf_exception_forced_emulation_test needs to be explicitly filtered out of the primary "vmx" test config.
