public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Manali Shukla <manali.shukla@amd.com>
Cc: pbonzini@redhat.com, kvm@vger.kernel.org, aaronlewis@google.com
Subject: Re: [kvm-unit-tests PATCH v2 0/4] x86: nSVM: Add testing for routing L2 exceptions
Date: Wed, 5 Oct 2022 21:14:46 +0000	[thread overview]
Message-ID: <Yz3zxo4zEZs8ryVu@google.com> (raw)
In-Reply-To: <20220810050738.7442-1-manali.shukla@amd.com>

On Wed, Aug 10, 2022, Manali Shukla wrote:
> Series is inspired by vmx exception test framework series[1].
> 
> Set up a test framework that verifies an exception occurring in L2 is
> forwarded to the right place (L1 or L2).
> 
> Tests two conditions for each exception.
> 1) Exception generated in L2, is handled by L2 when L2 exception handler
>    is registered.
> 2) Exception generated in L2, is handled by L1 when intercept exception
>    bit map is set in L1.
> 
> Above tests were added to verify 8 different exceptions.
> #GP, #UD, #DE, #DB, #AC, #OF, #BP, #NM.
> 
> There are 4 patches in this series
> 1) Added test infrastructure and exception tests.
> 2) Move #BP test to exception test framework.
> 3) Move #OF test to exception test framework.
> 4) Move part of #NM test to exception test framework because
>    #NM has a test case which checks the condition for which #NM should not
>    be generated, all the test cases under #NM test except this test case have been
>    moved to exception test framework because of the exception test framework
>    design.

I know Paolo NACKed a full rework to share nVMX and nSVM code, but it's super easy
to share the helpers, get a net -100 LoC, and improve nVMX coverage.

I've done the work, along with some misc cleanups.  I'll post a combined version
shortly.

 lib/x86/processor.h |  98 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 x86/svm_tests.c     | 195 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------------------------------------------
 x86/vmx_tests.c     | 200 +++++++++++--------------------------------------------------------------------------------------------------------------------------------------
 3 files changed, 199 insertions(+), 294 deletions(-)

      parent reply	other threads:[~2022-10-05 21:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10  5:07 [kvm-unit-tests PATCH v2 0/4] x86: nSVM: Add testing for routing L2 exceptions Manali Shukla
2022-08-10  5:20 ` [kvm-unit-tests PATCH v2 1/4] x86: nSVM: Add an exception test framework and tests Manali Shukla
2022-10-05 21:16   ` Sean Christopherson
2022-08-10  5:21 ` [kvm-unit-tests PATCH v2 2/4] x86: nSVM: Move #BP test to exception test framework Manali Shukla
2022-08-10  5:22 ` [kvm-unit-tests PATCH v2 3/4] x86: nSVM: Move #OF " Manali Shukla
2022-08-10  5:23 ` [kvm-unit-tests PATCH v2 4/4] x86: nSVM: Move part of #NM " Manali Shukla
2022-10-05 21:17   ` Sean Christopherson
2022-08-29  4:11 ` [kvm-unit-tests PATCH v2 0/4] x86: nSVM: Add testing for routing L2 exceptions Manali Shukla
2022-09-19  4:41   ` Manali Shukla
2022-09-26  4:34     ` Manali Shukla
2022-10-03  4:15       ` Manali Shukla
2022-10-03  7:07         ` Maxim Levitsky
2022-10-05 21:14 ` 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=Yz3zxo4zEZs8ryVu@google.com \
    --to=seanjc@google.com \
    --cc=aaronlewis@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=manali.shukla@amd.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox