xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Krish Sadhukhan <krish.sadhukhan@oracle.com>
To: Sergey Dyasli <sergey.dyasli@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH v1 3/3] x86/vvmx: add a shadow vmcs check to vmlaunch
Date: Thu, 16 Mar 2017 11:32:39 -0700	[thread overview]
Message-ID: <14a33bb1-9de4-0cce-c5f3-5c6b220e3a8d@oracle.com> (raw)
In-Reply-To: <6d105555-91e7-6d42-5306-8bcd0de5c27c@oracle.com>

Acknowledging it formally...

Reviewed-by: Krish Sadhukhan <krish.sadhukhan@oracle.com>

The review was based on Intel SDM chapters 24 and 30.

-Krish

On 03/16/2017 11:24 AM, Krish Sadhukhan wrote:
> This one looks good to me.
>
> -Krish
>
> On 03/13/2017 03:51 AM, Sergey Dyasli wrote:
>> Intel SDM states that if the current VMCS is a shadow VMCS,
>> VMFailInvalid occurs and control passes to the next instruction.
>>
>> Implement such behaviour for nested vmlaunch.
>>
>> Signed-off-by: Sergey Dyasli <sergey.dyasli@citrix.com>
>> ---
>>   xen/arch/x86/hvm/vmx/vvmx.c | 7 +++++++
>>   1 file changed, 7 insertions(+)
>>
>> diff --git a/xen/arch/x86/hvm/vmx/vvmx.c b/xen/arch/x86/hvm/vmx/vvmx.c
>> index 3017849..173ec74 100644
>> --- a/xen/arch/x86/hvm/vmx/vvmx.c
>> +++ b/xen/arch/x86/hvm/vmx/vvmx.c
>> @@ -1630,6 +1630,13 @@ int nvmx_handle_vmlaunch(struct cpu_user_regs 
>> *regs)
>>           return X86EMUL_OKAY;
>>       }
>>   +    /* Check that guest is not using a shadow vmcs for vmentry */
>> +    if ( nvmx->shadow_vmcs )
>> +    {
>> +        vmfail_invalid(regs);
>> +        return X86EMUL_OKAY;
>> +    }
>> +
>>       __vmread(GUEST_INTERRUPTIBILITY_INFO, &intr_shadow);
>>       if ( intr_shadow & VMX_INTR_SHADOW_MOV_SS )
>>       {
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2017-03-16 18:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13 10:51 [PATCH v1 0/3] x86/vvmx: fixes for mov-ss and shadow vmcs handling Sergey Dyasli
2017-03-13 10:51 ` [PATCH v1 1/3] x86/vvmx: add mov-ss blocking check to vmentry Sergey Dyasli
2017-03-13 10:59   ` Andrew Cooper
2017-03-14  9:00   ` Tian, Kevin
2017-03-16 18:23   ` Krish Sadhukhan
2017-03-17  9:00     ` Sergey Dyasli
2017-03-13 10:51 ` [PATCH v1 2/3] x86/vvmx: correct nested shadow VMCS handling Sergey Dyasli
2017-03-14  9:11   ` Tian, Kevin
2017-03-13 10:51 ` [PATCH v1 3/3] x86/vvmx: add a shadow vmcs check to vmlaunch Sergey Dyasli
2017-03-14  9:11   ` Tian, Kevin
2017-03-16 18:24   ` Krish Sadhukhan
2017-03-16 18:32     ` Krish Sadhukhan [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=14a33bb1-9de4-0cce-c5f3-5c6b220e3a8d@oracle.com \
    --to=krish.sadhukhan@oracle.com \
    --cc=sergey.dyasli@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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).