All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Winchell <dwinchell@virtualiron.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Dave Winchell <dwinchell@virtualiron.com>,
	"Tian, Kevin" <kevin.tian@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Pratt <Ian.Pratt@eu.citrix.com>,
	"dan.magenheimer@oracle.com" <dan.magenheimer@oracle.com>
Subject: Re: Re: Fix for get_s_time()
Date: Thu, 24 Apr 2008 14:32:39 -0400	[thread overview]
Message-ID: <4810D247.7040400@virtualiron.com> (raw)
In-Reply-To: <C43675C0.1FEDC%keir.fraser@eu.citrix.com>

Keir Fraser wrote:

>On 24/4/08 17:04, "Dave Winchell" <dwinchell@virtualiron.com> wrote:
>
>  
>
>>yes, this is the issue. What you suggest should be fine and I am trying
>>it now.
>>With the locking version (and a fix to a bug I introduced) I got .0012%
>>error
>>on an overnight run with hpet layered on get_s_time_mono(), which is the
>>max(prev, cur) layer on get_s_time we discussed.
>>    
>>
>
>12 parts per million is pretty good. Is that cumulative deviation from 'wall
>time' over ~12 hours?
>
yes, deviation between the guest's time and an ntp reference.

> That could easily be explained by the fact that Xen
>system time is not sync'ed with ntp.
>  
>
That's true. And, as we have discussed, this error seems to vary quite a bit
platform to platform for some reason. I will verify that this still is 
the case.

-Dave

> -- Keir
>
>
>  
>

  reply	other threads:[~2008-04-24 18:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47FFC37A.4060402@virtualiron.com>
2008-04-11 21:20 ` System time monotonicity Keir Fraser
2008-04-11 21:41   ` Keir Fraser
2008-04-11 22:58     ` Dave Winchell
2008-04-12  7:09       ` Keir Fraser
2008-04-21 19:26         ` Dan Magenheimer
2008-04-21 19:31           ` Keir Fraser
2008-04-21 20:32             ` Fix for get_s_time() Dave Winchell
2008-04-21 22:55               ` Keir Fraser
2008-04-21 23:10                 ` Keir Fraser
2008-04-22 14:09                   ` Dave Winchell
2008-04-24 16:04                   ` Dave Winchell
2008-04-24 16:37                     ` Keir Fraser
2008-04-24 18:32                       ` Dave Winchell [this message]
2008-04-25 19:48                         ` Dave Winchell
2008-04-25 21:03                           ` Dan Magenheimer
2008-04-26  1:54                             ` Dave Winchell
2008-04-28 17:39                               ` Dan Magenheimer
2008-04-28 18:09                                 ` Dave Winchell
2008-04-28 18:40                                   ` Dave Winchell
2008-04-29  7:14                                     ` Keir Fraser
2008-04-29 14:21                                       ` Dave Winchell
2008-04-28 20:11                                   ` Dan Magenheimer
2008-04-28 21:29                                     ` Dave Winchell
2008-04-11 22:22   ` System time monotonicity Dan Magenheimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4810D247.7040400@virtualiron.com \
    --to=dwinchell@virtualiron.com \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=kevin.tian@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.