From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@qumranet.com>
Subject: Stop the clock!
Date: Tue, 04 Mar 2008 12:47:58 +0200
Message-ID: <47CD28DE.7020502@qumranet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>
To: Glauber de Oliveira Costa <gcosta@redhat.com>
Return-path: <kvm-devel-bounces@lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/kvm-devel>,
	<mailto:kvm-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=kvm-devel>
List-Post: <mailto:kvm-devel@lists.sourceforge.net>
List-Help: <mailto:kvm-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/kvm-devel>,
	<mailto:kvm-devel-request@lists.sourceforge.net?subject=subscribe>
Sender: kvm-devel-bounces@lists.sourceforge.net
Errors-To: kvm-devel-bounces@lists.sourceforge.net
List-Id: kvm.vger.kernel.org

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.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
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/