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 17:08:03 -0400 [thread overview]
Message-ID: <20040928210803.GK921@cs.duke.edu> (raw)
In-Reply-To: <E1CCMTh-0000fT-00@mta1.cl.cam.ac.uk>
" None of this makes much sense. It's certainly worth instrumenting
" SETTIME.
I added a printk in do_dom0ops. I saw the same 70 minute jump ahead in
the system clock in domain 0 when I shutdown domain 1. I did not get any
new SETTIME printk from xm dmesg. The only settime calls occured when
dom0 booted and ntp started.
The client domains do not have CONFIG_XEN_PRIVILEGED_GUEST set and
nothing unusual is running on dom0. I start up xen0, then xenU, then
kill xenU and the xen0 date immediately jumps.
" No -- SETTIME effectively sets the dom0 system time, that Xen
" also exports to other domains.
So does that mean from the dom0 perspective that system time and hwclock
time should always be identical?
What hwclock says on dom0 did not change. Just what date says changed.
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-09-28 21:08 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
2004-09-28 18:13 ` Ian Pratt
2004-09-28 21:08 ` David Becker [this message]
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=20040928210803.GK921@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.