This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Re: [Xen-devel] Xen 4 TSC problems

To: Keir Fraser <keir@xxxxxxx>
Subject: [Xen-users] Re: [Xen-devel] Xen 4 TSC problems
From: Olivier Hanesse <olivier.hanesse@xxxxxxxxx>
Date: Thu, 24 Feb 2011 12:57:15 +0100
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>, Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>, Mark Adams <mark@xxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 24 Feb 2011 03:59:12 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=upmVkzcq7Nx1D8lqkfuz9eKcp4iVmqp7G70VKan16QI=; b=MClR2QVIwoeTq2FC9UvuI1Y21DquO0J8sKqiY1rlPD4Y7u2Y08VAzP20Qovm8rkJR5 afyOFZ8ZeF2Bn5x4jqHBALQut5gjYHjauArrxu6kYIkRQ5KP8WEiTweDCGICk2jh/X4C mpbRRrEIEZ2HbNxf6z4hgDL0txFcr5yYMy0ek=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=U9eCGwq0+TfmX11h4hVZcyhBGodgS7k7WjyOYJifxNxw3jHGdaS/eKoZreoEiPU7b8 zYbbLw+7lGTAUvp0Yf+n/gLdL4XcRApQqjI2zL2yAvZWE6AbQtCPWCvYz3MRCo202niu 914yC0usrrMC42kQoEOrspf7yMa+nUe7XF+Dk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C98BF1C4.2B3E6%keir@xxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4D6648220200007800033769@xxxxxxxxxxxxxxxxxx> <C98BF1C4.2B3E6%keir@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Jan :�

I tried to turn off cstates with max_cstate=0�without success (still "not reliable").

With cpuidle=0, I also got :

(XEN) TSC has constant rate, deep Cstates possible, so not reliable, warp=3022 (count=1)

xm info | grep command
xen_commandline � � � �: dom0_mem=512M cpuidle=0 loglvl=all guest_loglvl=all dom0_max_vcpus=1 dom0_vcpus_pin console=vga,com1 com1=19200,8n1

Keir :�

Using clocksource=pit :

(XEN) Platform timer is 1.193MHz PIT

I also got : �

(XEN) TSC has constant rate, deep Cstates possible, so not reliable, warp=3262 (count=2)

2011/2/24 Keir Fraser <keir@xxxxxxx>
On 24/02/2011 10:59, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:

>>>> On 24.02.11 at 10:59, Olivier Hanesse <olivier.hanesse@xxxxxxxxx> wrote:
>> (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times.
>> Output of xm debug-key s :
>> (XEN) TSC has constant rate, deep Cstates possible, so not reliable,
>> warp=2684 (count=4)
> Did you try turning of use of C states ("cpuidle=0" on the Xen
> command line)?

Another thing to try is changing the platform timer that Xen uses. It's
using HPET on your machines, so try clocksource=pit on Xen command line, and
confirm that the 'Platform timer is xxx' message changes in xm dmesg.

However, this bug looks more like a CPU's TSC jumping forward (or maybe
backward) for some inexplicable reason. We added code post 3.2 to detect the
platform timer counter wrapping, and to account for that based on trusting
the CPU's 64-bit TSC. But if the TSC value is bogus then we can detect a
wrap when it didn't happen and the new code will do more harm than good. It
is not currently possible to disable the code via a boto parameter -- maybe
we could add that. However, if the problem is a jumpy TSC then it is better
to fix that as Xen relies so heavily on TSC for time handling.

�-- Keir

> Jan

Xen-users mailing list