From: Paolo Bonzini <pbonzini@redhat.com>
To: Krish Sadhukhan <krish.sadhukhan@oracle.com>, kvm@vger.kernel.org
Cc: jmattson@google.com, seanjc@google.com, vkuznets@redhat.com,
wanpengli@tencent.com, joro@8bytes.org
Subject: Re: [PATCH 0/2 v2] Test: nSVM: Test the effect of guest EFLAGS.TF on VMRUN
Date: Mon, 26 Jul 2021 14:14:25 +0200 [thread overview]
Message-ID: <e1549127-8a11-cf5d-6ea3-890cbe14e374@redhat.com> (raw)
In-Reply-To: <20210719174617.241568-1-krish.sadhukhan@oracle.com>
On 19/07/21 19:46, Krish Sadhukhan wrote:
> v1 -> v2:
> In patch# 1, the new function is now called __svm_vmrun() per
> suggestion from Sean. I have also adjusted the commit header and
> the commit message.
>
>
> Patch# 1: Adds a variant of svm_vmrun() so that custom guest code can be used.
> Patch# 2: Tests the effects of guest EFLAGS.TF on VMRUN.
>
> [PATCH 1/2 v2] nSVM: Add a variant of svm_vmrun() for setting guest RIP
> [PATCH 2/2 v2] Test: nSVM: Test the effect of guest EFLAGS.TF on VMRUN
>
> x86/svm.c | 9 +++++++--
> x86/svm.h | 1 +
> x86/svm_tests.c | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 69 insertions(+), 2 deletions(-)
>
> Krish Sadhukhan (2):
> nSVM: Add a variant of svm_vmrun() for setting guest RIP to custom code
> Test: nSVM: Test the effect of guest EFLAGS.TF on VMRUN
>
Queued, thanks. However, I placed this in a different test than
svm_guest_state_test, since that one is more evaluating invalid (or
silently canonicalized) data.
Paolo
prev parent reply other threads:[~2021-07-26 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 17:46 [PATCH 0/2 v2] Test: nSVM: Test the effect of guest EFLAGS.TF on VMRUN Krish Sadhukhan
2021-07-19 17:46 ` [PATCH 1/2 v2] nSVM: Add a variant of svm_vmrun() for setting guest RIP to custom code Krish Sadhukhan
2021-07-19 17:46 ` [PATCH 2/2 v2] Test: nSVM: Test the effect of guest EFLAGS.TF on VMRUN Krish Sadhukhan
2021-07-26 12:14 ` 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=e1549127-8a11-cf5d-6ea3-890cbe14e374@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=krish.sadhukhan@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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.