[PATCH v2 1/2] timekeeping: add EXPORT_SYMBOL_GPL for do_adjtimex()

Thomas Shao huishao at microsoft.com
Tue Oct 21 04:55:57 UTC 2014


> -----Original Message-----
> From: Jeff Epler [mailto:jepler at unpythonic.net]
> Sent: Tuesday, October 21, 2014 12:02 PM
> To: Thomas Shao
> Cc: Thomas Gleixner; gregkh at linuxfoundation.org; LKML;
> devel at linuxdriverproject.org; olaf at aepfle.de; apw at canonical.com;
> jasowang at redhat.com; KY Srinivasan; John Stultz; Richard Cochran
> Subject: Re: [PATCH v2 1/2] timekeeping: add EXPORT_SYMBOL_GPL for
> do_adjtimex()
> 
> On Tue, Oct 21, 2014 at 03:18:58AM +0000, Thomas Shao wrote:
> > In some situation, the user is not able to enable guest VM to sync
> > with external time source, like NTP. But the host is still synced with a
> trusted time source.
> > In this case, host-guest time synchronization is useful.
> 
> It's interesting to imagine that a virtualization host could present a time
> service to the guest *userspace*, even when the guest is not otherwise
> exposed to the internet at large.  This could take the form of an NTP server
> on a private network, or as an implementation of a time source directly
> usable by ntpd in the guest, for instance as an emulated serial port with
> synthetic NEMA GPS signal + PPS signal, for instance.

Yeah. There is already some guidance about how to setup a local NTP server. But it 
requires some additional efforts for IT admins. I don't think we need configure
every host as a time source. Typically we could setup one server shared by the 
private network, and that server needs to be synced with upstream NTP server. 

I'm also thinking if NTPd could expose some interface to allow other application to
directly provide time source for it to consume. In my opinion, emulating the ntp 
source should be very hard and error prone.


More information about the devel mailing list