xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Wu, Feng" <feng.wu@intel.com>
Cc: "Jan Beulich (JBeulich@suse.com)" <JBeulich@suse.com>,
	"Wang, Yong Y" <yong.y.wang@intel.com>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: SMAP/SMEP issues with 32-bit pv guests
Date: Mon, 1 Aug 2016 11:16:03 +0100	[thread overview]
Message-ID: <fc0a8cf7-dc73-783d-b638-cc411ec27aee@citrix.com> (raw)
In-Reply-To: <E959C4978C3B6342920538CF579893F019731A3E@SHSMSX103.ccr.corp.intel.com>

On 28/06/16 02:58, Wu, Feng wrote:
> Hi Andy,
>
> As you know, SMAP/SMEP may affect the 32-bit pv guests, after discussed internally, our current idea is that we can just disable this two feature for Xen hypervisor itself, hence only enable it for HVM guests. Do you think this is acceptable from your perspective?

So you are suggesting that Xen detects SMEP/SMAP, doesn't turn it on for
itself, but does allow HVM guests to use it?

I suppose that is a slight improvement over the current situation.

~Andrew

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

  parent reply	other threads:[~2016-08-01 10:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28  1:58 SMAP/SMEP issues with 32-bit pv guests Wu, Feng
2016-06-28  7:41 ` Jan Beulich
2016-08-01  0:48   ` Wu, Feng
2016-08-01  8:16     ` Jan Beulich
2016-08-01  8:25       ` Wu, Feng
2016-08-01 10:16 ` Andrew Cooper [this message]
2016-08-01 12:24   ` Wang, Yong Y
2016-08-01 12:30     ` Andrew Cooper
2016-08-01 12:48       ` Wu, Feng

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=fc0a8cf7-dc73-783d-b638-cc411ec27aee@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=feng.wu@intel.com \
    --cc=jun.nakajima@intel.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yong.y.wang@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).