|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation
To: |
Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> |
Subject: |
Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation |
From: |
Avi Kivity <avi@xxxxxxxxxx> |
Date: |
Thu, 29 Oct 2009 17:07:26 +0200 |
Cc: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>, kurt.hackel@xxxxxxxxxx, Glauber Costa <glommer@xxxxxxxxxx>, the arch/x86 maintainers <x86@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Glauber de Oliveira Costa <gcosta@xxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, zach.brown@xxxxxxxxxx, Ingo Molnar <mingo@xxxxxxxxxx>, chris.mason@xxxxxxxxxx |
Delivery-date: |
Thu, 29 Oct 2009 08:08:17 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<6137c066-3dfd-49dd-bbf2-7718f8542958@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> |
References: |
<6137c066-3dfd-49dd-bbf2-7718f8542958@default> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Thunderbird/3.0b4 |
On 10/29/2009 04:46 PM, Dan Magenheimer wrote:
No, the apps I'm familiar with (a DB and a JVM) need a timestamp
not a monotonic counter. The timestamps must be relatively
accurate (e.g. we've been talking about gettimeofday generically,
but these apps would use clock_gettime for nsec resolution),
monotonically increasing, and work properly across a VM
migration. The timestamps are taken up to a 100K/sec or
more so the apps need to ensure they are using the fastest
mechanism available that meets those requirements.
Out of interest, do you know (and can you relate) why those apps need
100k/sec monotonically increasing timestamps?
--
error compiling committee.c: too many arguments to function
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, (continued)
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Jeremy Fitzhardinge
- RE: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Dan Magenheimer
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Avi Kivity
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Glauber Costa
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Avi Kivity
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Avi Kivity
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Chris Mason
- RE: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Dan Magenheimer
- Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation,
Avi Kivity <=
- RE: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Dan Magenheimer
- RE: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation, Dan Magenheimer
- [Xen-devel] pvclock implementation in pv_ops kernel: why not __native_read_tsc()?, Dan Magenheimer
- [Xen-devel] Re: pvclock implementation in pv_ops kernel: why not __native_read_tsc()?, Jeremy Fitzhardinge
|
|
|
|
|