Re: [PATCH] x86/pvclock-xen: zero last_value on resume

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Glauber Costa
Date: Tuesday, October 26, 2010 - 10:48 am

On Tue, 2010-10-26 at 09:59 -0700, Jeremy Fitzhardinge wrote:
After migration, save/restore, etc, we issue an ioctl where we tell
the host the last clock value. That (in theory) guarantees monotonicity.

I am not opposed to this patch in any way, however.


--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH] x86/pvclock-xen: zero last_value on resume, Jeremy Fitzhardinge, (Tue Oct 26, 9:59 am)
Re: [PATCH] x86/pvclock-xen: zero last_value on resume, Glauber Costa, (Tue Oct 26, 10:48 am)
Re: [Xen-devel] Re: [PATCH] x86/pvclock-xen: zero last_val ..., Jeremy Fitzhardinge, (Wed Oct 27, 11:53 am)
Re: [PATCH] x86/pvclock-xen: zero last_value on resume, Jeremy Fitzhardinge, (Mon Nov 22, 1:16 pm)
Re: [PATCH] x86/pvclock-xen: zero last_value on resume, Ingo Molnar, (Fri Nov 26, 3:40 am)
Re: [PATCH] x86/pvclock-xen: zero last_value on resume, Jeremy Fitzhardinge, (Fri Nov 26, 3:29 pm)