All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manali Shukla <manali.shukla@amd.com>
To: pbonzini@redhat.com, seanjc@google.com
Cc: 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: Mon, 3 Oct 2022 09:45:41 +0530	[thread overview]
Message-ID: <23878d4c-52ec-9a07-1189-7a547ec9c9d0@amd.com> (raw)
In-Reply-To: <bae31123-27ae-5996-affb-93a7199a66f1@amd.com>

On 9/26/2022 10:04 AM, Manali Shukla wrote:
> On 9/19/2022 10:11 AM, Manali Shukla wrote:
>> On 8/29/2022 9:41 AM, Manali Shukla wrote:
>>> On 8/10/2022 10:37 AM, 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.
>>>>
>>>> v1->v2
>>>> 1) Rebased to latest kvm-unit-tests. 
>>>> 2) Move 3 different exception test cases #BP, #OF and #NM exception to
>>>>    exception test framework.
>>>>
>>>> [1] https://lore.kernel.org/all/20220125203127.1161838-1-aaronlewis@google.com/
>>>> [2] https://lore.kernel.org/kvm/a090c16f-c307-9548-9739-ceb71687514f@amd.com/
>>>>
>>>> Manali Shukla (4):
>>>>   x86: nSVM: Add an exception test framework and tests
>>>>   x86: nSVM: Move #BP test to exception test framework
>>>>   x86: nSVM: Move #OF test to exception test framework
>>>>   x86: nSVM: Move part of #NM test to exception test framework
>>>>
>>>>  x86/svm_tests.c | 197 ++++++++++++++++++++++++++++++++++--------------
>>>>  1 file changed, 142 insertions(+), 55 deletions(-)
>>>>
>>>
>>> A gentle reminder for the review
>>>
>>> -Manali
>>
>> A gentle reminder for the review
>>
>> -Manali
> 
> A gentle reminder for the review
> 
> -Manali

A gentle remider for the review

-Manali


  reply	other threads:[~2022-10-03  4:16 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 [this message]
2022-10-03  7:07         ` Maxim Levitsky
2022-10-05 21:14 ` Sean Christopherson

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=23878d4c-52ec-9a07-1189-7a547ec9c9d0@amd.com \
    --to=manali.shukla@amd.com \
    --cc=aaronlewis@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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.