From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] call write_guest_time as soon as we register the paravirt clock. Date: Fri, 22 Feb 2008 09:47:01 +0200 Message-ID: <47BE7DF5.4020602@qumranet.com> References: <1203627854-4216-1-git-send-email-gcosta@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net, chrisw@sous-sol.org To: Glauber de Oliveira Costa Return-path: In-Reply-To: <1203627854-4216-1-git-send-email-gcosta@redhat.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 Glauber de Oliveira Costa wrote: > From: Glauber Costa > > In situations, like, cpu hotplugging, a cpu can arrive > later on the game and register its paravirt clock > while everything else is already running, which will lead to > breakage, since the time readings will return bogus values. > > To prevent this, we write system time as soon as the guest > registers its clock > Applied, thanks. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- 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/