From: Sergey Dyasli <sergey.dyasli@citrix.com>
To: "krish.sadhukhan@oracle.com" <krish.sadhukhan@oracle.com>
Cc: Sergey Dyasli <sergey.dyasli@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v1 1/3] x86/vvmx: add mov-ss blocking check to vmentry
Date: Fri, 17 Mar 2017 09:00:25 +0000 [thread overview]
Message-ID: <1489741225.2880.0.camel@citrix.com> (raw)
In-Reply-To: <0b61ea60-8766-d669-769e-3de28cae9cc6@oracle.com>
On Thu, 2017-03-16 at 11:23 -0700, Krish Sadhukhan wrote:
> The Intel SDM also mentions POP-SS. Are you planning to do it via
> another patch ?
(SDM from Dec 2016) In "Table 24-3. Format of Interruptibility State"
it reads "This document uses the term “blocking by MOV SS,” but it
applies equally to POP SS."
>
> Also, I was wondering if it makes more sense to rename the new enum code as
>
> VMX_INSN_VMENTRY_BLOCKED
>
> since it can then also be used for POP-SS.
--
Thanks,
Sergey
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-17 9:00 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 [this message]
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
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=1489741225.2880.0.camel@citrix.com \
--to=sergey.dyasli@citrix.com \
--cc=krish.sadhukhan@oracle.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 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.