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

[Xen-devel] [Q] about clock_gettime accuracy on i386(&x86_64).

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [Q] about clock_gettime accuracy on i386(&x86_64).
From: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>
Date: Tue, 12 Jun 2007 18:34:19 +0900
Delivery-date: Tue, 12 Jun 2007 02:33:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

I am now compareing clock_gettime() accuracy 
between Native Linux and Dom0.(i386 and x86_64)

Dom0 accuracy is microsecond.
(nanosecond 3-digit is not changed keep some value)
But Linux accuracy is nanosecond.
(nanosecond 3-digit is changed each clock_gettime call)

Is there any plan to fix this?
Or would you tell me the reason?

Thanks
Atsushi SAKAI




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

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