Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932814AbaJVLBp (ORCPT ); Wed, 22 Oct 2014 07:01:45 -0400 Received: from mail-ig0-f174.google.com ([209.85.213.174]:64824 "EHLO mail-ig0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932458AbaJVLBo (ORCPT ); Wed, 22 Oct 2014 07:01:44 -0400 MIME-Version: 1.0 In-Reply-To: References: <1413362372-16236-1-git-send-email-huishao@microsoft.com> <20141021040212.GA6278@unpythonic.net> <20141021082058.GB6808@netboy> Date: Wed, 22 Oct 2014 12:01:43 +0100 Message-ID: Subject: Re: [PATCH v2 1/2] timekeeping: add EXPORT_SYMBOL_GPL for do_adjtimex() From: Mike Surcouf To: Thomas Shao Cc: Richard Cochran , Jeff Epler , Thomas Gleixner , "gregkh@linuxfoundation.org" , LKML , "devel@linuxdriverproject.org" , "olaf@aepfle.de" , "apw@canonical.com" , "jasowang@redhat.com" , KY Srinivasan , John Stultz , Richard Cochran Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I get that NTP can be installed locally. This is how I regulate time on my guests. I agree the admin argument probably doesn't stand up. The problem is hyperv_clocksource (pluggable time source used by hyperv guests) is systematically fast in my environment. by around -250 PPM. I get away with NTP (just). However others have had to use tickadj to get hyperv_clocksource close enough for NTP to work i.e. inside +/-500 PPM. (This IS outside normal admin tasks) So if we are going to use NTP as the solution for hyperv guests (which is a valid one) the systematic drift of hyperv_clocksource in different environments will need to be addressed. Maybe this patch could be modified to tune the tick count on boot before NTP starts and then leave it alone so NTP can take over. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/