On Wed, Feb 02, 2011 at 07:16:20AM -0500, Glauber Costa wrote: > If the machine is stopped, we should not record two different tsc values > upon a save operation. The same problem happens with kvmclock. > > But kvmclock is taking a different diretion, being now seen as a separate > device. Since this is unlikely to happen with the tsc, I am taking the > approach here of simply registering a handler for state change, and > using a per-CPUState variable that prevents double updates for the TSC. > > Signed-off-by: Glauber Costa <glommer@xxxxxxxxxx> > CC: Jan Kiszka <jan.kiszka@xxxxxx> > > --- > v2: updated tsc validation logic, as asked by Jan > --- > target-i386/cpu.h | 1 + > target-i386/kvm.c | 18 +++++++++++++++++- > 2 files changed, 18 insertions(+), 1 deletions(-) Please regenerate against uq/master. -- 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
