From: Paolo Bonzini <pbonzini@redhat.com>
To: Manali Shukla <manali.shukla@amd.com>, kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH 0/3] Add L2 exception handling KVM unit tests for nSVM
Date: Tue, 18 Jan 2022 10:21:29 +0100 [thread overview]
Message-ID: <d6e6d814-bcbb-b4a0-04cb-8f90dcbf68e4@redhat.com> (raw)
In-Reply-To: <20211229062201.26269-1-manali.shukla@amd.com>
On 12/29/21 07:21, Manali Shukla wrote:
> This series adds 3 KVM Unit tests for nested SVM
> 1) Check #NM is handled in L2 when L2 #NM handler is registered
> "fnop" instruction is called in L2 to generate the exception
>
> 2) Check #BP is handled in L2 when L2 #BP handler is registered
> "int3" instruction is called in L2 to generate the exception
>
> 3) Check #OF is handled in L2 when L2 #OF handler is registered
> "into" instruction with instrumented code is used in L2 to
> generate the exception
>
> Manali Shukla (3):
> x86: nSVM: Check #NM exception handling in L2
> x86: nSVM: Check #BP exception handling in L2
> x86: nSVM: Check #OF exception handling in L2
>
> x86/svm_tests.c | 114 ++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 114 insertions(+)
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2022-01-18 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 6:21 [kvm-unit-tests PATCH 0/3] Add L2 exception handling KVM unit tests for nSVM Manali Shukla
2021-12-29 6:21 ` [kvm-unit-tests PATCH 1/3] x86: nSVM: Check #NM exception handling in L2 Manali Shukla
2021-12-29 6:22 ` [kvm-unit-tests PATCH 2/3] x86: nSVM: Check #BP " Manali Shukla
2021-12-29 6:22 ` [kvm-unit-tests PATCH 3/3] x86: nSVM: Check #OF " Manali Shukla
2022-01-07 4:05 ` [kvm-unit-tests PATCH 0/3] Add L2 exception handling KVM unit tests for nSVM Shukla, Manali
2022-01-12 21:29 ` Sean Christopherson
2022-01-18 11:11 ` Shukla, Manali
2022-01-18 11:38 ` Paolo Bonzini
2022-01-18 9:21 ` Paolo Bonzini [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=d6e6d814-bcbb-b4a0-04cb-8f90dcbf68e4@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=manali.shukla@amd.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;
as well as URLs for NNTP newsgroup(s).