All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, Mathias Krause <minipli@grsecurity.net>
Subject: Re: [kvm-unit-tests PATCH v4 9/9] nVMX: Add forced emulation variant of #PF access test
Date: Tue, 4 Apr 2023 12:45:59 -0700	[thread overview]
Message-ID: <ZCx+d8eSrNWccvTF@google.com> (raw)
In-Reply-To: <20230404165341.163500-10-seanjc@google.com>

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@google.com>
> ---
>  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.

      reply	other threads:[~2023-04-04 19:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 16:53 [kvm-unit-tests PATCH v4 0/9] x86/access: CR0.WP=0/1 r/o tests Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 1/9] x86: Use existing CR0.WP / CR4.SMEP bit definitions Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 2/9] x86/access: CR0.WP toggling write to r/o data test Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 3/9] x86/access: Replace spaces with tabs in access_test.c Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 4/9] x86/access: Use standard pass/fail reporting machinery Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 5/9] x86/access: Add forced emulation support Sean Christopherson
2023-04-04 18:49   ` Sean Christopherson
2023-04-04 23:43     ` Sean Christopherson
2023-04-05 11:29   ` Mathias Krause
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 6/9] x86/access: Try forced emulation for CR0.WP test as well Sean Christopherson
2023-04-05 11:48   ` Mathias Krause
2023-04-05 14:29     ` Sean Christopherson
2023-04-05 15:41       ` Mathias Krause
2023-04-05 19:41         ` Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 7/9] x86: Drop VPID invl tests from nested reduced MAXPHYADDR access testcase Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 8/9] x86: Mark the VPID invalidation nested VMX access tests nodefault Sean Christopherson
2023-04-04 16:53 ` [kvm-unit-tests PATCH v4 9/9] nVMX: Add forced emulation variant of #PF access test Sean Christopherson
2023-04-04 19:45   ` Sean Christopherson [this message]

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=ZCx+d8eSrNWccvTF@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=minipli@grsecurity.net \
    --cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.