WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchroniz

To: Joanna Rutkowska <joanna@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchronization
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 06 Jul 2010 09:17:38 -0700
Cc: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Jeremy Fitzhardinge <Jeremy.Fitzhardinge@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Rafal Wojtczuk <rafal@xxxxxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 06 Jul 2010 09:18:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C32F367.2090302@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C8527CEA.1930A%keir.fraser@xxxxxxxxxxxxx> <4C322FF9.1050601@xxxxxxxx> <4C32602B.3090108@xxxxxxxxxxxxxxxxxxxxxx> <4C3261C8.4000808@xxxxxxxx> <4C3264B0.5090605@xxxxxxxxxxxxxxxxxxxxxx> <4C326898.6040709@xxxxxxxx> <4C32F367.2090302@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc12 Lightning/1.0b2pre Thunderbird/3.0.4
On 07/06/2010 02:12 AM, Joanna Rutkowska wrote:
>> CLOCK_MONOTONIC is directly derived from the Xen system time, so it will
>> presumably pause while the machine is suspended.  CLOCK_REALTIME is just
>> the Xen system time with an offset added to make the normal Unix TOD; if
>> the offset isn't updated after resume, then it will also not advance
>> over the suspend.
>>
>>     
> What is an easy way to dump all those clocks, like e.g. via some /proc
> entry?
>   

They're available via the clock_gettime function in librt.  I don't know
if there's a standard utility which allows them to be displayed/called.

    J


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>