| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 26 Oct 2010 08:49:22 -0200 From: Glauber Costa <glommer@...hat.com> To: Avi Kivity <avi@...hat.com> Cc: Jeremy Fitzhardinge <jeremy@...p.org>, 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 Tue, 2010-10-26 at 10:14 +0200, Avi Kivity wrote: > 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. the suspend/resume path do adjust the time base. Maybe something similar should be done ? -- 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