From mboxrd@z Thu Jan 1 00:00:00 1970 From: Glauber Costa Subject: Re: Stop the clock! Date: Tue, 04 Mar 2008 09:41:33 -0300 Message-ID: <47CD437D.3000406@redhat.com> References: <47CD28DE.7020502@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: Avi Kivity Return-path: In-Reply-To: <47CD28DE.7020502@qumranet.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Avi Kivity wrote: > With paravirt clocksource, reboot and kexec are broken: the clock keeps > updating after the reboot, and the new kernel will have a random memory > location trampled occasionally. > > So we need to stop the clock on kexec (in the guest) and reboot (in the > host). On the host side, this can be done either in the kernel, or in > userspace via new ioctls. > > Joerg, I think you mentioned you were working on a vm-wide reset > ioctl()? If so, that would be the place to stop the clock on reboot. > > Glauber, can you extend the interface to support stopping the clock? It > needs to be done even outside kexec, for example if the the user decides > to stop using your clock. > Sure, I'll work on it. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/