From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: Xen HVM regression on certain Intel CPUs Date: Wed, 27 Mar 2013 10:44:28 -0700 Message-ID: <51532FFC.6000106@zytor.com> References: <51530F9F.10805@canonical.com> <515315EC.4030803@canonical.com> <20130327160427.GB6688@phenom.dumpdata.com> <5153222B.3030605@canonical.com> <51532C43.8010808@canonical.com> <51532CA1.6030809@zytor.com> <51532EF5.6090300@canonical.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51532EF5.6090300@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: wei.y.yang@intel.com, "xen-devel@lists.xensource.com" , haitao.shan@intel.com, xin.li@intel.com, Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 03/27/2013 10:40 AM, Stefan Bader wrote: > On 27.03.2013 18:30, H. Peter Anvin wrote: >> On 03/27/2013 10:28 AM, Stefan Bader wrote: >>> >>> I will need more time to look into this (and unlikely today) >>> but it feels like at least the cpuid flags passed on to HVM >>> guest may be not influenced by the smep boot argument. Probably >>> rather something I could do by masking in the config of the >>> guest (which could be another pain as I normally configure >>> those via libvirt). >>> >> >> There is an "nosmep" kernel command line option. > > Ignoring it on that side does help. > As one would expect. Are CPUID and /proc/cpuinfo still consistent across all CPUs inside the HVM? -hpa