[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51A4F6C6.8080808@citrix.com>
Date: Tue, 28 May 2013 19:26:14 +0100
From: David Vrabel <david.vrabel@...rix.com>
To: John Stultz <john.stultz@...aro.org>
CC: Jan Beulich <JBeulich@...e.com>,
Thomas Gleixner <tglx@...utronix.de>,
"xen-devel@...ts.xen.org" <xen-devel@...ts.xen.org>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH 2/3] timekeeping: sync persistent clock and
RTC on system time step changes
On 15/05/13 19:10, John Stultz wrote:
>
> Ok, so really, as soon as the Dom0 time is set by NTP, all guests will
> see the right time? That makes more sense, and means the window for
> these sorts of issues is reasonably quite small.
It's a small window but it's occurring in our automated test system.
> David: So I'm less inclined to merge this individual change, but if you
> still feel strongly about it, let me know and we can circle around on it
> after you've addressed the specific issues I pointed out earlier.
This patch was the actual bug fix but I've reworked it to use the
pvclock_gtod notifier chain as this seemed to be what KVM hosts were
using to maintain a clock for guests. Please review the new series, thanks.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists