kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Krish Sadhukhan <krish.sadhukhan@oracle.com>, kvm@vger.kernel.org
Cc: jmattson@google.com, sean.j.christopherson@intel.com
Subject: Re: [PATCH 0/2 v2] kvm-unit-test: nVMX: Test GUEST_BNDCFGS VM-Entry control on vmentry of nested guests
Date: Wed, 18 Mar 2020 14:07:00 +0100	[thread overview]
Message-ID: <0d142825-07ee-daec-6238-33bf916ffdb0@redhat.com> (raw)
In-Reply-To: <1584472530-31728-1-git-send-email-krish.sadhukhan@oracle.com>

On 17/03/20 20:15, Krish Sadhukhan wrote:
> v1 -> v2:
> 	Rebased to the latest Upstream repo. No other changes.
> 
> 
> Patch# 1: Adds the required enum values to the header file
> Patch# 2: Adds the test code
> 
> [PATCH 1/2 v2] kvm-unit-test: VMX: Add enum for GUEST_BNDCFGS field and LOAD_BNDCFGS
> [PATCH 2/2 v2] kvm-unit-test: nVMX: Test GUEST_BNDCFGS VM-Entry control on vmentry of
> 
>  x86/vmx.h       |  2 ++
>  x86/vmx_tests.c | 45 +++++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 47 insertions(+)
> 
> Krish Sadhukhan (2):
>       VMX: Add enum for GUEST_BNDCFGS field and LOAD_BNDCFGS vmentry control fie
>       nVMX: Test GUEST_BNDCFGS VM-Entry control on vmentry of nested guests
> 

Queued, thanks.

Paolo


      parent reply	other threads:[~2020-03-18 13:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 19:15 [PATCH 0/2 v2] kvm-unit-test: nVMX: Test GUEST_BNDCFGS VM-Entry control on vmentry of nested guests Krish Sadhukhan
2020-03-17 19:15 ` [PATCH 1/2 v2] kvm-unit-test: VMX: Add enum for GUEST_BNDCFGS field and LOAD_BNDCFGS vmentry control field Krish Sadhukhan
2020-03-17 19:15 ` [PATCH 2/2 v2] kvm-unit-test: nVMX: Test GUEST_BNDCFGS VM-Entry control on vmentry of nested guests Krish Sadhukhan
2020-03-18 13:07 ` 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=0d142825-07ee-daec-6238-33bf916ffdb0@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jmattson@google.com \
    --cc=krish.sadhukhan@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=sean.j.christopherson@intel.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).