All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Becker <becker@cs.duke.edu>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: repeatable time jump
Date: Tue, 28 Sep 2004 14:00:24 -0400	[thread overview]
Message-ID: <20040928180024.GI921@cs.duke.edu> (raw)
In-Reply-To: <E1CCM1u-0000LT-00@mta1.cl.cam.ac.uk>


" Weird. I can't reproduce.

I can reproduce it on that host, but most hosts don't have the problem.

" The only way that I can see that xen's system time can be changed
" is via the DOM0_SETTIME dom0 op.

Its the system time in domain 0 that is changing.   The time dom0 gets
by reading hwclock is ok.  Would hwclock time be what DOM0_SETTIME sets?



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl

  reply	other threads:[~2004-09-28 18:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 15:06 repeatable time jump David Becker
2004-09-28 15:11 ` repeatable time jump typo David Becker
2004-09-28 17:44 ` repeatable time jump Ian Pratt
2004-09-28 18:00   ` David Becker [this message]
2004-09-28 18:13     ` Ian Pratt
2004-09-28 21:08       ` David Becker
2004-09-28 21:29         ` Ian Pratt
2004-09-29 17:32           ` David Becker
2004-09-29 17:46             ` Ian Pratt
2004-09-29 18:28               ` David Becker
2004-09-30 20:46                 ` Ian Pratt
2004-10-01 14:00                   ` David Becker
2004-10-01 15:21                     ` Ian Pratt
2004-10-01 17:03                       ` David Becker
2004-10-01 17:26                       ` Adam Heath
2004-10-02  8:36                       ` Peri Hankey

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=20040928180024.GI921@cs.duke.edu \
    --to=becker@cs.duke.edu \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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.