From: Stefan Bader <stefan.bader@canonical.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
wei.y.yang@intel.com, haitao.shan@intel.com,
Keir Fraser <keir.xen@gmail.com>,
xin.li@intel.com
Subject: Re: Xen HVM regression on certain Intel CPUs
Date: Thu, 28 Mar 2013 17:12:56 +0100 [thread overview]
Message-ID: <51546C08.5040900@canonical.com> (raw)
In-Reply-To: <515464DA.90405@zytor.com>
[-- Attachment #1.1: Type: text/plain, Size: 656 bytes --]
On 28.03.2013 16:42, H. Peter Anvin wrote:
> On 03/28/2013 08:06 AM, Stefan Bader wrote:
>>
>> No you are completely right. The inverse boolean got me for good.
>> So to summarize:
>>
>> - smep=0 as hypervisor argument avoids the problem for all guests -
>> nosmep as hvm guest arguement avoids the problem for that guest -
>> /proc/cpuinfo correctly reflects whether smep has been masked off
>> or not
>>
>
> Please try to patch Jan pointed to.
I did, but it did not work. Elaborating on it a bit more in the reply I wrote to
his mail. In short, I think the code that would clear smep is not reached.
-Stefan
>
> -hpa
>
>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-03-28 16:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 15:26 Xen HVM regression on certain Intel CPUs Stefan Bader
2013-03-27 15:53 ` Stefan Bader
2013-03-27 16:04 ` Konrad Rzeszutek Wilk
2013-03-27 16:09 ` H. Peter Anvin
2013-03-27 16:24 ` Stefan Bader
2013-03-27 16:32 ` H. Peter Anvin
2013-03-27 16:32 ` Stefano Stabellini
2013-03-27 16:45 ` Stefan Bader
2013-03-27 16:52 ` H. Peter Anvin
2013-03-27 17:17 ` Stefan Bader
2013-03-27 17:23 ` H. Peter Anvin
2013-03-27 17:38 ` Stefan Bader
2013-03-28 13:34 ` Jan Beulich
2013-03-28 15:02 ` Stefan Bader
2013-03-28 16:39 ` Stefan Bader
2013-04-03 11:56 ` Stefan Bader
2013-04-03 12:43 ` Jan Beulich
2013-04-03 14:28 ` Keir Fraser
2013-04-03 15:00 ` Xu, Dongxiao
2013-04-03 15:48 ` H. Peter Anvin
2013-04-03 16:05 ` Jan Beulich
2013-03-27 17:28 ` Stefan Bader
2013-03-27 17:30 ` H. Peter Anvin
2013-03-27 17:40 ` Stefan Bader
2013-03-27 17:44 ` H. Peter Anvin
2013-03-27 20:24 ` Keir Fraser
2013-03-28 15:06 ` Stefan Bader
2013-03-28 15:42 ` H. Peter Anvin
2013-03-28 16:12 ` Stefan Bader [this message]
2013-03-27 16:18 ` H. Peter Anvin
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=51546C08.5040900@canonical.com \
--to=stefan.bader@canonical.com \
--cc=haitao.shan@intel.com \
--cc=hpa@zytor.com \
--cc=keir.xen@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=wei.y.yang@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xin.li@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 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.