From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joanna Rutkowska Subject: Re: S3 sleep in dom0 breaks dom0<->domU wallclock synchronization Date: Tue, 06 Jul 2010 11:12:07 +0200 Message-ID: <4C32F367.2090302@invisiblethingslab.com> References: <4C322FF9.1050601@goop.org> <4C32602B.3090108@invisiblethingslab.com> <4C3261C8.4000808@goop.org> <4C3264B0.5090605@invisiblethingslab.com> <4C326898.6040709@goop.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0381916277==" Return-path: In-Reply-To: <4C326898.6040709@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: Jeremy Fitzhardinge , "xen-devel@lists.xensource.com" , Keir Fraser , Rafal Wojtczuk , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0381916277== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig730C6F88C3914A0196C2F661" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig730C6F88C3914A0196C2F661 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 07/06/10 01:19, Jeremy Fitzhardinge wrote: > On 07/05/2010 04:03 PM, Joanna Rutkowska wrote: >> I guess all these other clocks have nothing to do with RTC/wallclock, >> right? They are effectively just like any other system timers (they ar= e >> system timers), and they are updated by the timer interrupt and they >> don't need RTC to be happy? So, I would say they are fine, just like a= ll >> the other timers, as otherwise I would expect DomUs to explode/hang >> after resume. >> =20 >=20 > CLOCK_MONOTONIC is directly derived from the Xen system time, so it wil= l > presumably pause while the machine is suspended. CLOCK_REALTIME is jus= t > the Xen system time with an offset added to make the normal Unix TOD; i= f > the offset isn't updated after resume, then it will also not advance > over the suspend. >=20 What is an easy way to dump all those clocks, like e.g. via some /proc entry? j. --------------enig730C6F88C3914A0196C2F661 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/ iEYEARECAAYFAkwy82cACgkQORdkotfEW87fOACfcIK4eajM8W9Or7f8U6JREOjb cfAAoO/al37i58FbH+hqI4cqZPe2+PE0 =HD2S -----END PGP SIGNATURE----- --------------enig730C6F88C3914A0196C2F661-- --===============0381916277== 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 --===============0381916277==--