From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: 2.6.35-rc1 regression with pvclock and smp guests
Date: Sun, 03 Oct 2010 10:22:58 +0200
Message-ID: <4CA83D62.8060406@redhat.com>
References: <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> <4CA4AD87.8060502@redhat.com> <4CA4DBC8.6070606@xutrox.com> <20100930190507.GA1111@amt.cnet> <4CA51715.1070507@msgid.tls.msk.ru> <4CA51847.5060208@msgid.tls.msk.ru> <4CA6C4BB.5020004@redhat.com> <4CA6E0BF.90605@msgid.tls.msk.ru> <4CA7AA38.1080005@redhat.com> <4CA83BEC.9020701@msgid.tls.msk.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Zachary Amsden <zamsden@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Arjan Koers <0h61vkll2ly8@xutrox.com>, kvm@vger.kernel.org,
	Glauber Costa <glommer@redhat.com>,
	Andre Przywara <andre.przywara@amd.com>, jeremy@xensource.com
To: Michael Tokarev <mjt@tls.msk.ru>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:37835 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752358Ab0JCIXJ (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 3 Oct 2010 04:23:09 -0400
In-Reply-To: <4CA83BEC.9020701@msgid.tls.msk.ru>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

  On 10/03/2010 10:16 AM, Michael Tokarev wrote:
> I just booted this same guest using kvm-0.12.5 - using that one
> guest does not report unstable tsc, yet does not list it in the
> available_clocksources.  It also shows time jumps:
>
> ...
> [0;0/0:    0.000000] Detected 3217.424 MHz processor.
> [0;0/0:    0.006666] Calibrating delay loop (skipped) preset value.. 6437.96 BogoMIPS (lpj=10724746)
> [0;0/0:    0.006666] pid_max: default: 32768 minimum: 301
> [0;0/0:    0.006666] Mount-cache hash table entries: 512
> [0;0/0:    0.006765] Initializing cgroup subsys ns
> ...
> [0;0/0:    0.029999] Booting Node   0, Processors  #1 Ok.
> [1;0/0:    0.006666] Initializing CPU#1
> [1;0/0:    0.006666] kvm-clock: cpu 1, msr 0:1e0a0c1, secondary cpu clock
> [0;0/0:    0.058342] Brought up 2 CPUs
> ...

Most likely it's still using jiffies while the clocks are being set up.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.