This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] syncing wall clock time from Dom0 to hypervisor

To: <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] syncing wall clock time from Dom0 to hypervisor
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Wed, 13 Jul 2011 15:37:18 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 13 Jul 2011 07:38:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> 07/13/11 3:52 PM >>>
>Looking at xen_set_wallclock it just looks as we need to make it do
>a similar hypercall as the sync_xen_wallclock to update it?

I would think so.

>I think the 'sync_cmos_clock' looks to be doing that. And the hook
>to the Xen is via 'update_persistent_clock' call?

The problem is that Xen code overwites the x86_platform.[gs]et_wallclock
hooks, without calling (at least in the set case on Dom0) the original
function afaics.

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-devel] syncing wall clock time from Dom0 to hypervisor, Jan Beulich <=