From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 3/3] xen/privcmd: add IOCTL_PRIVCMD_SYNC_WALLCLOCK to sync Xen's wallclock
Date: Fri, 12 Oct 2012 17:30:03 +0100 [thread overview]
Message-ID: <5078458B.7090901@citrix.com> (raw)
In-Reply-To: <20121012161610.GA7880@phenom.dumpdata.com>
On 12/10/12 17:16, Konrad Rzeszutek Wilk wrote:
>
> So, having both ntpd (which calls call adjtimex) - which would run in the
> background; and hwclock run at startup - (which updates the RTC, which ends
> - I hope - being trapped by the hypervisor), we end up with the correct
> time, right?
Yes, unless you start a guest before ntpd has synchronized.
David
next prev parent reply other threads:[~2012-10-12 16:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 12:57 [PATCH 0/3] xen: fix various wallclock problems David Vrabel
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 [this message]
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=5078458B.7090901@citrix.com \
--to=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=konrad@kernel.org \
--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 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.