Vitaly,
On Tue, 10 Jan 2017, Vitaly Kuznetsov wrote:
> Thomas Gleixner writes:
> > 1) do_adjtimex() is assuming that there is a single client connected which
> >is responsible for the updates. So I seriously doubt that a NTP client
> >running in the guest will cooperate nicely with that t
Thomas Gleixner writes:
> On Wed, 4 Jan 2017, Vitaly Kuznetsov wrote:
>
>> Changes since v1:
>> - do do_settimeofday64() when ICTIMESYNCFLAG_SYNC flag is present in the
>> request (Alex Ng)
>> - add pr_debug() for the case when do_adjtimex() fails (Alex Ng)
>>
>> Original description:
>>
>> W
On Wed, 4 Jan 2017, Vitaly Kuznetsov wrote:
> Changes since v1:
> - do do_settimeofday64() when ICTIMESYNCFLAG_SYNC flag is present in the
> request (Alex Ng)
> - add pr_debug() for the case when do_adjtimex() fails (Alex Ng)
>
> Original description:
>
> With TimeSync version 4 protocol suppo
Changes since v1:
- do do_settimeofday64() when ICTIMESYNCFLAG_SYNC flag is present in the
request (Alex Ng)
- add pr_debug() for the case when do_adjtimex() fails (Alex Ng)
Original description:
With TimeSync version 4 protocol support we started updating system time
continuously through the w
