From: David Vrabel <david.vrabel@citrix.com>
To: xen-devel@lists.xen.org
Cc: David Vrabel <david.vrabel@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: [PATCH 0/3] xen: fix various wallclock problems
Date: Fri, 12 Oct 2012 13:57:11 +0100 [thread overview]
Message-ID: <1350046634-2462-1-git-send-email-david.vrabel@citrix.com> (raw)
This series (with some toolstack updates) corrects a number of cases
where a guest can see an incorrect wallclock time.
1. Systems with NTP won't periodically synchronize the hardware RTC so
the wallclock may be incorrect after a reboot.
2. The wallclock is always ~500 ms behind the correct time.
3. If the system time was stepped and NTP isn't synchronized yet, the
wallclock will still have the incorrect time. The fix for this
requires the toolstack to synchronize the wallclock -- patch #3
provides the mechanism for this.
David
next reply other threads:[~2012-10-12 12:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 12:57 David Vrabel [this message]
2012-10-12 12:57 ` [PATCH 1/3] xen: sync the CMOS RTC as well as the Xen wallclock David Vrabel
2012-10-12 14:57 ` Konrad Rzeszutek Wilk
2012-10-12 16:13 ` David Vrabel
2012-10-12 12:57 ` [PATCH 2/3] xen: add correct 500 ms offset when setting " David Vrabel
2012-10-15 9:25 ` Ian Campbell
2012-10-15 12:21 ` David Vrabel
2012-10-15 12:27 ` Ian Campbell
2012-10-12 12:57 ` [PATCH 3/3] xen/privcmd: add IOCTL_PRIVCMD_SYNC_WALLCLOCK to sync Xen's wallclock David Vrabel
2012-10-12 13:41 ` Konrad Rzeszutek Wilk
2012-10-12 14:02 ` David Vrabel
2012-10-12 14:29 ` Konrad Rzeszutek Wilk
2012-10-12 14:59 ` David Vrabel
2012-10-12 15:02 ` Konrad Rzeszutek Wilk
2012-10-12 16:14 ` David Vrabel
2012-10-12 16:16 ` Konrad Rzeszutek Wilk
2012-10-12 16:30 ` David Vrabel
2012-10-12 16:25 ` [PATCH 0/3] xen: fix various wallclock problems David Vrabel
2012-10-15 9:26 ` Ian Campbell
2012-10-15 12:23 ` David Vrabel
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=1350046634-2462-1-git-send-email-david.vrabel@citrix.com \
--to=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).