From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Xen 4 TSC problems Date: Thu, 24 Feb 2011 12:37:53 +0000 Message-ID: <4D665F3102000078000337B6@vpn.id2.novell.com> References: <4D6648220200007800033769@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Olivier Hanesse Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com, Keir Fraser , Dan Magenheimer , Xen Users , Mark Adams List-Id: xen-devel@lists.xenproject.org >>> On 24.02.11 at 12:57, Olivier Hanesse = wrote: > I tried to turn off cstates with max_cstate=3D0 without success (still = "not > reliable"). >=20 > With cpuidle=3D0, I also got : >=20 > (XEN) TSC has constant rate, deep Cstates possible, so not reliable, > warp=3D3022 (count=3D1) This message by itself isn't telling much I believe. > xm info | grep command > xen_commandline : dom0_mem=3D512M cpuidle=3D0 loglvl=3Dall = guest_loglvl=3Dall > dom0_max_vcpus=3D1 dom0_vcpus_pin console=3Dvga,com1 com1=3D19200,8n1 >=20 > Keir : >=20 > Using clocksource=3Dpit : >=20 > (XEN) Platform timer is 1.193MHz PIT >=20 > I also got : >=20 > (XEN) TSC has constant rate, deep Cstates possible, so not reliable, > warp=3D3262 (count=3D2) The question is whether any of this eliminates the time jumps seen by your DomU-s (from your past mails I wasn't actually sure whether Dom0 also experienced this problem, albeit it would be odd if it didn't). Jan Jan