Messages in this thread | | | Date | Thu, 29 Oct 2009 17:07:26 +0200 | From | Avi Kivity <> | Subject | Re: [Xen-devel] Re: [PATCH 3/5] x86/pvclock: add vsyscall implementation |
| |
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
| |