From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joanna Rutkowska Subject: Re: A clocksource question Date: Thu, 11 Mar 2010 01:15:20 +0100 Message-ID: <4B983618.9030004@invisiblethingslab.com> References: <4B962748.90609@invisiblethingslab.com> <4B96DB69.10101@goop.org 4B981997.4030605@invisiblethingslab.com> <56cc3abf-21f6-4178-b00e-0331538080d9@default> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0699859609==" Return-path: In-Reply-To: <56cc3abf-21f6-4178-b00e-0331538080d9@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0699859609== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig5971F1398A148B6CBB016434" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5971F1398A148B6CBB016434 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 03/11/2010 01:07 AM, Dan Magenheimer wrote: >> Clocksource tsc unstable (delta =3D 62752834 ns) >> hrtimer: interrupt too slow, forcing clock min delta to 412700358 ns >> >>> I don't remember if 3.4.2 ended up with tsc emulation, but if it does= >>> you might try enabling it. >>> >> >> TSC emulation? But I'm running only PV guests. Not sure what do you >> mean >> by this, or how to enable it? >=20 > I don't think there is any TSC emulation (or more properly "rdtsc emula= tion") > in 3.4.x, certainly not without a special Xen boot option. >=20 > The TSC delta is troubling... Actually I'm getting this also when booting Dom0 (pvops 2.6.31.6-based) with clocksource=3Djifffies: Clocksource tsc unstable (delta =3D 62528016 ns) But, there are not visible problems like kbd hiccup or process scheduling in VM (besides wallclock drift in Dom0 which is annoying). > if you hadn't said you had turned > off all power management, I would have guessed a problem with > C-state management. Maybe Xen is discovering some power management > capability not visible in BIOS settings? >=20 I'm not very much of an ACPI expert, so if there are any output I can send, just let me know. j. --------------enig5971F1398A148B6CBB016434 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkuYNiAACgkQORdkotfEW84EgACfcXQaxXaEyNimPzZaQ8Z/AikW izEAni94zHNTmiHyw4ddeOolZH93X9Mq =H+B1 -----END PGP SIGNATURE----- --------------enig5971F1398A148B6CBB016434-- --===============0699859609== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0699859609==--