From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: syncing wall clock time from Dom0 to hypervisor Date: Thu, 30 Jun 2011 11:16:17 +0100 Message-ID: <4E0C6911020000780004B45B@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org While in the upstream kernel I'm unable to find any use of XENPF_settime (and the DOM0_SETTIME alias of it) at all, in the 2.6.18 tree (and the forward ports of it) the function gets used only when ntp_synced() returns true (and - that's minor - when independent_wallclock is not set). It would however seem to me that this doesn't cover the case where the host clock gets adjusted by the Dom0 admin. Is there perhaps someone who remembers whether this was implemented the way it is intentionally? There's no such restriction in Jeremy's tree, but that tree also doesn't seem to be doing updates at regular intervals (for NTP), nor does it look like the CMOS clock would get updated here at all (i.e. I can't really take this as a proper reference either). Thanks, Jan