From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zachary Amsden Subject: Re: 2.6.35-rc1 regression with pvclock and smp guests Date: Thu, 30 Sep 2010 05:32:23 -1000 Message-ID: <4CA4AD87.8060502@redhat.com> References: <4C4D4B8B.80006@amd.com> <4C4DDB00.50203@xutrox.com> <4C4F48D0.8090609@xutrox.com> <4C500872.1020809@redhat.com> <4C536F80.5090205@xutrox.com> <4C538CCE.1010104@redhat.com> <4C540EC9.1010008@xutrox.com> <4C54512B.6000307@xutrox.com> <4C54B7DE.4060901@redhat.com> <20100802144300.GD14448@mothafucka.localdomain> <4C5729F6.2050605@redhat.com> <4C573A20.6030001@xutrox.com> <4CA2F8A3.80400@redhat.com> <4CA30424.9030007@msgid.tls.msk.ru> <4CA30493.6090503@msgid.tls.msk.ru> <4CA392FE.5090009@xutrox.com> <4CA4427C.9090304@msgid.tls.msk.ru> <4CA45F7B.8050806@msgid.tls.msk.ru> <4CA4968F.9050402@redhat.com> <4CA4A8C5.3030407@msgid.tls.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Arjan Koers <0h61vkll2ly8@xutrox.com>, kvm@vger.kernel.org, Avi Kivity , Glauber Costa , Andre Przywara To: Michael Tokarev Return-path: Received: from mx1.redhat.com ([209.132.183.28]:36433 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932083Ab0I3Pca (ORCPT ); Thu, 30 Sep 2010 11:32:30 -0400 In-Reply-To: <4CA4A8C5.3030407@msgid.tls.msk.ru> Sender: kvm-owner@vger.kernel.org List-ID: On 09/30/2010 05:12 AM, Michael Tokarev wrote: > 30.09.2010 17:54, Zachary Amsden wrote: > [] > >> The printk movement is just a bandaid patch, correct? Anything which >> does printk before kvmclock is registered could trigger the same bug. >> > Well, I'd not say it's just a bandaid patch, it's real bug -- either > we can read kvmclock (so it's initialized), or we don't touch it (at > least before registration). > Yes, that's the bug, but moving the printk doesn't fix that, it just hides it. > >> Can you try with printk timing disabled and see if the bug disappears? >> > Yes it disappears so far, at last I can't trigger it anymore, tried > numerous boots including the 2.6.35.6 32bit kernel (patched with the > printk registration patch!) which shows the prob in almost every boot. > So, looks like we need to do the real fix. Zach