Bug#534978: clock drift in Xen domU with clocksource=xen
On Thu, Feb 25, 2010 at 12:18:54PM +0100, Josip Rodin wrote:
> Using jiffies as a clock source is not a "solution", it's a workaround,
> because its resolution (CONFIG_HZ^1) is not good enough for reading
> microseconds, that is, time with microseconds will become just monotonic.
> This will cause problems for any program that wants its time readouts to
> be strictly increasing, as real-world time usually is :)
No. The time resolution is not defined and within one step it will
always provide the same value.
> and it also caused occasional PostgreSQL errors
> with tables that had timestamp columns as keys, since it became possible
> for two independent transactions to come in at the exact same time.
Äh, where is documented, that this supposed to work anyway?
Bastian
--
Killing is stupid; useless!
-- McCoy, "A Private Little War", stardate 4211.8
Reply to: