From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S939061AbdAIR6h (ORCPT <rfc822;w@1wt.eu>);
        Mon, 9 Jan 2017 12:58:37 -0500
Received: from mail-pf0-f175.google.com ([209.85.192.175]:33424 "EHLO
        mail-pf0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S936661AbdAIR6f (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 9 Jan 2017 12:58:35 -0500
Date: Mon, 9 Jan 2017 09:58:27 -0800
From: Stephen Hemminger <stephen@networkplumber.org>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: "Alex Ng \(LIS\)" <alexng@microsoft.com>,
        Haiyang Zhang <haiyangz@microsoft.com>,
        "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        John Stultz <john.stultz@linaro.org>,
        "devel\@linuxdriverproject.org" <devel@linuxdriverproject.org>,
        Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 3/4] hv_util: use do_adjtimex() to update system time
Message-ID: <20170109095827.0cc364ad@xeon-e3>
In-Reply-To: <87lguk6sjk.fsf@vitty.brq.redhat.com>
References: <20170102194114.657-1-vkuznets@redhat.com>
        <20170102194114.657-4-vkuznets@redhat.com>
        <MWHPR03MB2734B2657BA19D402C0ED1A6D86F0@MWHPR03MB2734.namprd03.prod.outlook.com>
        <87a8b8qq7d.fsf@vitty.brq.redhat.com>
        <MWHPR03MB2734DBEDA866670F5AA8BFBBD86E0@MWHPR03MB2734.namprd03.prod.outlook.com>
        <20170109091950.7d7be8da@xeon-e3>
        <87lguk6sjk.fsf@vitty.brq.redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, 09 Jan 2017 18:40:15 +0100
Vitaly Kuznetsov <vkuznets@redhat.com> wrote:

> Stephen Hemminger <stephen@networkplumber.org> writes:
> 
> > An alternative would be for hyper-v util to provide a clocksource device and
> > let NTP manage the adjustment. The advantage of this would be HV util not fighting
> > with NTP, and using standard API's. The downside would be the complexity of configuring
> > NTP, and difficulty of writing a clock source pseudo device.  
> 
> Yes, I see this option. But as I wrote to John I'm afraid we'll have to
> come up with a custom interface from hv_util to userspace which no NTP
> server will want to support (because, first of all, it's not about
> 'network time' any more). We can write our own daemon which will read
> from this interface and do adjtimex but in this case I don't see much
> value in this data traveling from kernel to userspace and back...
> 

Master NTP servers are connected to authoritative clock sources. I have no idea how
that is configured, but it should be possible.