[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: Jan Beulich <JBeulich@xxxxxxxxxx>, Olivier Hanesse <olivier.hanesse@xxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Thu, 24 Feb 2011 11:30:12 +0000
  • Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>, Mark Adams <mark@xxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 24 Feb 2011 03:31:43 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=D75PjlUG96y8XNdLyJ5r94942rwUnuhvS+UnLMI8ef/L7W0YCcDMhSFYFvNiRRV7PV /bdYfOTe6YN0unWgnHhzttuk+LewV9mXPjQEg80T3cb/vwyfQsG7g41BYDnAjO1AUN+v 7PLLbPOYJDRjfKNZHM6AdisFzrF4zdUqUuNfg=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcvUFjL8NYHxWnUgn0Gfj4v2U6o5ig==
  • Thread-topic: [Xen-devel] Xen 4 TSC problems

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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.