On 09/02/2009 03:21 PM, Glauber Costa wrote:
+static void kvm_sync_wall_clock(struct work_struct *work)
+{
+ struct timespec now;
+
+ kvm_get_wall_ts(&now);
What happens if we schedule here?
hummm, I guess disabling preemption would be enough to make us safe here?
You can't prevent host preemption. You might read kvmclock again and
repeat if too much time has passed.
--
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
