From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [PATCHv3 0/2] xen: maintain an accurate persistent clock in more cases Date: Fri, 31 May 2013 08:52:50 +0100 Message-ID: <51A872F202000078000D9E5B__23061.9670045146$1369986886$gmane$org@nat28.tlf.novell.com> References: <1369923919-26981-1-git-send-email-david.vrabel@citrix.com> <51A7E709.9080309@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51A7E709.9080309@linaro.org> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: David Vrabel , John Stultz Cc: Thomas Gleixner , Konrad Rzeszutek Wilk , linux-kernel@vger.kernel.org, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org >>> On 31.05.13 at 01:55, John Stultz wrote: > The first is probably the easiest, but I do want to make sure that Xen > maintainers agree that Xen really needs to be special here compared to > every other platform and always enforce the RTC is synced with system time. Actually, during the v2 discussion I think we made clear that this is not the goal: Sync-ing of the RTC should be just like native does it. The only special thing Xen wants is that the hypervisor's software wall clock wants to be kept up to date when NTP or whatever else updates Dom0's wall clock. Jan