| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: pvclock in userland (reprise)
|
To: |
"Nakajima, Jun" <jun.nakajima@xxxxxxxxx> |
|
Subject: |
[Xen-devel] Re: pvclock in userland (reprise) |
|
From: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
|
Date: |
Thu, 17 Sep 2009 12:24:14 -0700 |
|
Cc: |
Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel \(E-mail\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Dugger, Donald D" <donald.d.dugger@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx> |
|
Delivery-date: |
Thu, 17 Sep 2009 12:24:37 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<0B53E02A2965CE4F9ADB38B34501A3A19411DC3F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
|
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> |
|
References: |
<f53b9652-8419-4a69-925c-47ea6e82fd85@default> <C6D8469E.15100%keir.fraser@xxxxxxxxxxxxx> <0B53E02A2965CE4F9ADB38B34501A3A19411DC3F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3 |
On 09/17/09 12:13, Nakajima, Jun wrote:
> Maybe you can write a device driver in the guest that sets up mapping against
> the (virtual) physical memory, then use mmap() in the app?
>
Dan is trying to avoid making guest kernel changes, on the grounds that
waiting for enterprise distros to catch up would take too long.
Once you're making kernel changes then you can update the pvclock
mechanism to use the xen clock algorithm, obviating the need for
usermode ABI changes.
However, if its really the case that the tsc is guaranteed synchronized,
then the guest can determine that for itself by looking at cpuid and/or
/proc/cpuinfo (and presumably doing some sanity checking) and then just
directly use rdtsc, with no need to change either Xen or the kernel.
J
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home