Thomas Gleixner writes:
> On Fri, 13 Jan 2017, Vitaly Kuznetsov wrote:
>> With TimeSync version 4 protocol support we started updating system time
>> continuously through the whole lifetime of Hyper-V guests. Every 5 seconds
>> there is a time sample from the host which triggers do_settimeofday[6
On Fri, 13 Jan 2017, Vitaly Kuznetsov wrote:
> With TimeSync version 4 protocol support we started updating system time
> continuously through the whole lifetime of Hyper-V guests. Every 5 seconds
> there is a time sample from the host which triggers do_settimeofday[64]().
> While the time from the
Richard Cochran writes:
>> +struct ptp_clock_info ptp_hyperv_info = {
>> +.name = "hyperv",
>> +.enable = hv_ptp_enable,
>> +.gettime64 = hv_ptp_gettime,
>
> The code in drivers/ptp/ptp_clock.c calls
>
> .adjfreq (or adjfine)
> .adjtime
> .sett
Olaf Hering writes:
> On Fri, Jan 13, Vitaly Kuznetsov wrote:
>
>> +hv_ptp_clock = ptp_clock_register(&ptp_hyperv_info, NULL);
>> +if (IS_ERR(hv_ptp_clock)) {
>
> Should that be IS_ERR_OR_NULL to catch "!IS_REACHABLE(CONFIG_PTP_1588_CLOCK)"?
>
Oh, yes. I missed the case when CONFIG_PTP_1
On Fri, Jan 13, Vitaly Kuznetsov wrote:
> + hv_ptp_clock = ptp_clock_register(&ptp_hyperv_info, NULL);
> + if (IS_ERR(hv_ptp_clock)) {
Should that be IS_ERR_OR_NULL to catch "!IS_REACHABLE(CONFIG_PTP_1588_CLOCK)"?
Olaf
signature.asc
Description: PGP signature
__
On Fri, Jan 13, 2017 at 02:05:43PM +0100, Vitaly Kuznetsov wrote:
> Instead of doing in-kernel time adjustments offload the work to an
> NTP client by exposing TimeSync messages as a PTP device. Users my now
> decide what they want to use as a source.
>
> I tested the solution with chrony, the con
