WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: rdtsc: correctness vs performance on Xen (and KVM?)

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: rdtsc: correctness vs performance on Xen (and KVM?)
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 01 Sep 2009 16:08:37 +0100
Cc: "Xen-Devel \(E-mail\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 01 Sep 2009 08:09:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <fedf16d3-e7a6-4272-9d56-23d0f6e358a2@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: AcorFALBqID28A1JTYGyQRYDpMdEoQAAhHxj
Thread-topic: rdtsc: correctness vs performance on Xen (and KVM?)
User-agent: Microsoft-Entourage/12.19.0.090515
On 01/09/2009 15:53, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> 1) fake rdmsr (or hypercall if it works) returns a virtual
>    address within a range of addresses that is not "owned by"
>    the OS (e.g. maybe in Xen address space?).  The page is
>    only readable outside of ring 0, but writeable in ring 0
>    (by Xen).
> 2) All TLB misses on this page are handled directly by Xen
>    so the OS never sees the address/page.

I think these are probably possible, at least for a 64-bit hypervisor which
isn't playing segment limit tricks.

> If these are OK, and you see other parts of the proposal
> that require PV kernel mods, please point them out.

Won't the pvclock computation be per-cpu? How will you deal with that?

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel