From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
Jan Beulich <JBeulich@novell.com>,
"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] pvcpuid: mask TSC invariant bit for various circumstances
Date: Wed, 28 Oct 2009 17:29:03 +0000 [thread overview]
Message-ID: <C70E2FDF.18AF4%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <b0087c25-282e-4715-96ac-3e13d60923ad@default>
Yes, CPUID is always trapped for HVM guests.
-- Keir
On 28/10/2009 16:50, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:
> Hmmm... this could be a real problem for some apps!
>
> Is this only a problem for PV domains? I.e, is cpuid
> always trapped by Xen for HVM domains?
>
>> -----Original Message-----
>> From: Jan Beulich [mailto:JBeulich@novell.com]
>> Sent: Wednesday, October 28, 2009 10:39 AM
>> To: Keir Fraser; Xen-Devel (E-mail); Dan Magenheimer
>> Subject: RE: [Xen-devel] [PATCH] pvcpuid: mask TSC invariant bit for
>> various circumstances
>>
>>>>> Dan Magenheimer <dan.magenheimer@oracle.com> 28.10.09 17:27 >>>
>>> But, that said, I'm still not convinced my patch is the
>>> right answer. If possible (e.g. using the CPUID masking
>>> feature Jan referred to), Xen should always hide the TSC
>>
>> Actually I just realized that this feature would probably not help you
>> at all: The bit you're after is in leaf 0x80000007, but the
>> masking applies
>> only to leaf 1 (plus 0x80000001 for AMD).
>>
>>> Invariant bit from all guests (OS's and apps) and only
>>> expose it via pvcpuid or some other mechanism.
>>> Otherwise an OS or app may make false assumptions
>>> based on an architecturally-specified cpuid bit.
>>
>> Jan
>>
>>
next prev parent reply other threads:[~2009-10-28 17:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 23:12 [PATCH] pvcpuid: mask TSC invariant bit for various circumstances Dan Magenheimer
2009-10-27 0:22 ` Keir Fraser
2009-10-27 1:09 ` Dan Magenheimer
2009-10-27 7:31 ` Keir Fraser
2009-10-27 17:03 ` Dan Magenheimer
2009-10-27 17:16 ` Keir Fraser
2009-10-27 20:40 ` Dan Magenheimer
2009-10-27 20:58 ` Keir Fraser
2009-10-27 22:03 ` Dan Magenheimer
2009-10-28 7:16 ` Keir Fraser
2009-10-28 16:27 ` Dan Magenheimer
2009-10-28 16:38 ` Jan Beulich
2009-10-28 16:50 ` Dan Magenheimer
2009-10-28 17:29 ` Keir Fraser [this message]
2009-10-29 22:07 ` Jeremy Fitzhardinge
2009-10-29 22:17 ` Dan Magenheimer
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=C70E2FDF.18AF4%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=dan.magenheimer@oracle.com \
--cc=xen-devel@lists.xensource.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.