On 09/02/2009 03:48 PM, Glauber Costa wrote:
You can't prevent host preemption. You might read kvmclock again and
repeat if too much time has passed.
But then you can be scheduled after you did settimeofday, but before reading
kvmclock again. Since we're aiming for periodic adjustments here,
any discrepancies should not last long, so we can maybe live with it.
do {
read_kvmclock
settimeofday
read_kvmclock
} while the_difference_between_the_two_reads_is_too_large
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
