From: Thomas Gleixner <tglx@linutronix.de>
To: Thomas Shao <huishao@microsoft.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"apw@canonical.com" <apw@canonical.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
KY Srinivasan <kys@microsoft.com>,
John Stultz <john.stultz@linaro.org>,
Richard Cochran <rcochran@linutronix.de>
Subject: RE: [PATCH v2 1/2] timekeeping: add EXPORT_SYMBOL_GPL for do_adjtimex()
Date: Tue, 21 Oct 2014 10:19:06 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1410210946470.5308@nanos> (raw)
In-Reply-To: <CD2CABCB2C0A0D4682C5F8AD840141540D27B9@HKXPRD3002MB006.064d.mgd.msft.net>
On Tue, 21 Oct 2014, Thomas Shao wrote:
> > I still do not have a consistent argument from you WHY you need to abuse
> > do_adjtimex() to do that host - guest synchronization in the first place.
> >
>
> I need a function to gradually slew guest time. do_adjtimex() provides all the
> functionality. Also I could not find any other exposed func to do this. I'd like to
> hear any feedback from you for this.
As Richard and others told you already, there are various options:
1) Use NTP on that private network, which does not involve any kernel
changes at all.
Your argument, that this is hard for IT-Admins to set up is just
ridiculous. If an IT-Admin is not able to set that up, then he
should better stay away from setting up a guest in the first place,
really.
2) As pointed out already by others PPS/PTP might be a proper solution
for this.
All it takes is a pair of timestamps (host/guest) injected into the
proper subsystem and a controlling daemon on the guest side. That
would also avoid the problem of running NTPd and your kernel side
poor mans NTPd at the same time.
That pseudo NTP thing is just hilarious, really.
You take the host time stamp in timesync_onchannelcallback() and
schedule work. From the work queue you correlate the host time
stamp to the current time of the guest. So you correlate time
stamps which can be an arbitrary time apart. Brilliant solution
that, really.
Thanks,
tglx
next prev parent reply other threads:[~2014-10-21 8:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 8:39 Thomas Shao
2014-10-20 18:28 ` Thomas Gleixner
2014-10-20 18:40 ` Thomas Gleixner
2014-10-21 3:18 ` Thomas Shao
2014-10-21 3:24 ` John Stultz
2014-10-21 4:08 ` Thomas Shao
2014-10-21 8:23 ` Thomas Gleixner
2014-10-21 4:02 ` Jeff Epler
2014-10-21 4:55 ` Thomas Shao
2014-10-21 8:25 ` Thomas Gleixner
2014-10-21 8:20 ` Richard Cochran
2014-10-21 10:11 ` Thomas Shao
2014-10-22 11:01 ` Mike Surcouf
2014-10-22 12:42 ` Thomas Gleixner
2014-10-22 13:51 ` Thomas Shao
2014-10-22 14:20 ` Mike Surcouf
2014-10-21 8:13 ` Richard Cochran
2014-10-21 9:16 ` Thomas Shao
2014-10-21 8:19 ` Thomas Gleixner [this message]
2014-10-21 9:02 ` Thomas Shao
2014-10-21 2:37 ` Thomas Shao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.11.1410210946470.5308@nanos \
--to=tglx@linutronix.de \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=huishao@microsoft.com \
--cc=jasowang@redhat.com \
--cc=john.stultz@linaro.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=rcochran@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®