[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CC68DE1.1060604@redhat.com>
Date: Tue, 26 Oct 2010 10:14:25 +0200
From: Avi Kivity <avi@...hat.com>
To: Jeremy Fitzhardinge <jeremy@...p.org>
CC: Glauber Costa <glommer@...hat.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org,
Marcelo Tosatti <mtosatti@...hat.com>,
Zachary Amsden <zamsden@...hat.com>,
"Xen-devel@...ts.xensource.com" <Xen-devel@...ts.xensource.com>
Subject: Re: [PATCH 1/5] Add a global synchronization point for pvclock
On 10/26/2010 01:30 AM, Jeremy Fitzhardinge wrote:
> Unfortunately this is breaking Xen save/restore: if you restore on a
> host which was booted more recently than the save host, causing the
> system time to be smaller. The effect is that the domain's time leaps
> forward to a fixed point, and stays there until the host catches up to
> the source host...
Shouldn't save/restore also save the timebase?
> I guess last_time needs to be reset on this type of event. I guess the
> cleanest way would be for pvclock.c to register a sysdev suspend/resume
> handler.
Should be for Xen only; kvm save/restore doesn't involve the guest.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists