This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: TSC scaling and softtsc reprise, and PROPOSAL

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: TSC scaling and softtsc reprise, and PROPOSAL
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 23 Jul 2009 16:45:39 +0100
Cc: "Dong, Eddie" <eddie.dong@xxxxxxxxx>, John Levon <levon@xxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 23 Jul 2009 08:46:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bec3a283-f6df-480e-8dc9-4e412d33cc7e@default>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcoLqNaDrd9Z0d1ORjmL3HNxCSeLEQAA8oQu
Thread-topic: TSC scaling and softtsc reprise, and PROPOSAL
User-agent: Microsoft-Entourage/
On 23/07/2009 16:18, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

>> pre-VT it wasn't possible to trap RDTSC, so this can't help PV guests.
> For PV guests, CR4.TSD would always be set, generating
> a general protection fault for every rdtsc.  (Or perhaps
> I am missing some x86 architectural subtlety?  This is
> how it is done on ia64.)

Forgot about CR4.TSD. Of course it's not going to be a super fast path,
since #GP(0) will need to be demuxed by decoding the faulting instruction in
the hypervisor, via a not-so-short path.

 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>