All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ferenc Wagner <wferi@niif.hu>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: XenParavirtOps wiki page updates
Date: Fri, 19 Dec 2008 17:32:16 -0800	[thread overview]
Message-ID: <494C4B20.3080708@goop.org> (raw)
In-Reply-To: <87k59vk940.fsf@szonett.ki.iif.hu>

Ferenc Wagner wrote:
> Hmm, my last data points are from the summer, but since people keep
> constantly asking on the users' list how to do this, I assumed things
> didn't change.  Back then ntpd was unable to change the domU clock, it
> was constantly drifting away from the current time.

Ah.  I've never tested it, but I've never got a bug report about it 
either.   The Xen clocksource's rate should be tuneable down to ~1ppm, 
which should be fine for ntp.

>   Also, when the
> procfs settings (like independent_wallclock) disappeared I got the
> impression that the system times are now unconditionally synced.
>   

No, the opposite - its never synced, except at domain boot.

> Probably I'm just confused and all is well now...  I'll set up and
> test this again.  Thanks for the hint!
>   

Please keep me informed.  RH has been shipping pvops kernels for a while 
now, and their stock install starts ntp.  I would have assumed that I'd 
have heard about any time sync problems by now...

    J

  reply	other threads:[~2008-12-20  1:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-13 19:33 XenParavirtOps wiki page updates Todd Deshane
2008-12-15 11:55 ` Ferenc Wagner
2008-12-15 12:01   ` Ian Campbell
2008-12-16 10:25     ` William Dauchy
2008-12-19 20:53   ` Jeremy Fitzhardinge
2008-12-20  0:01     ` Ferenc Wagner
2008-12-20  1:32       ` Jeremy Fitzhardinge [this message]
2008-12-22 14:59         ` Ferenc Wagner

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=494C4B20.3080708@goop.org \
    --to=jeremy@goop.org \
    --cc=wferi@niif.hu \
    --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.