From: Stefan Bader <stefan.bader@canonical.com>
To: xen-devel@lists.xen.org
Subject: Re: Xen HVM regression on certain Intel CPUs
Date: Wed, 27 Mar 2013 18:38:36 +0100 [thread overview]
Message-ID: <51532E9C.7020806@canonical.com> (raw)
In-Reply-To: <51532B2F.60506@zytor.com>
[-- Attachment #1.1: Type: text/plain, Size: 1317 bytes --]
On 27.03.2013 18:23, H. Peter Anvin wrote:
> On 03/27/2013 10:17 AM, Stefan Bader wrote:
>>> What does x86info and /proc/cpuinfo show in HVM?
>>
>> x86info cpuid[7].ebx = 0xbbb and /proc/cpuinfo also shows smep
>> set.
>
> On all CPUs?
x86info thinks its one core with ht so only one cpuid line for that.
>
>>> The inbound %cr4 shouldn't matter at all, we try to not rely on
>>> it.
>>>
>>> If the hypervisor presents SMEP to the guest then the guest is
>>> pretty obviously going to try to use it.
>>
>> To me it looks like when bootstrapping the APs things are not yet
>> ready to use it. If I did not miss something, the only place that
>> the saved contents of cr4 are used is in startup_32 when the cpus
>> are brought up. And then just stop dead. Would need to read more
>> code but a bit weird why the BP is not affected.
>
> This feels like a bug in Xen, but I don't know for sure yet. Either
> which way, it is odd. That write to cr4 should be entirely legitimate.
Could likely be. Unfortunately one where a change in the kernel triggers it. Not
exactly your problem but a pita nonetheless.
-Stefan
>
> -hpa
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
[-- 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-27 17:38 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 [this message]
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
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=51532E9C.7020806@canonical.com \
--to=stefan.bader@canonical.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 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).