From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: Xen HVM regression on certain Intel CPUs Date: Thu, 28 Mar 2013 08:42:18 -0700 Message-ID: <515464DA.90405@zytor.com> References: <51545C7D.2040608@canonical.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51545C7D.2040608@canonical.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefan Bader Cc: "xen-devel@lists.xensource.com" , Konrad Rzeszutek Wilk , wei.y.yang@intel.com, haitao.shan@intel.com, Keir Fraser , xin.li@intel.com List-Id: xen-devel@lists.xenproject.org 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. -hpa