From owner-svn-src-all@FreeBSD.ORG Thu Mar 24 23:26:15 2011 Return-Path: Delivered-To: svn-src-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E3651065687; Thu, 24 Mar 2011 23:26:15 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id F17EE8FC15; Thu, 24 Mar 2011 23:26:14 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id p2ONJSf4035381; Thu, 24 Mar 2011 17:19:28 -0600 (MDT) (envelope-from imp@bsdimp.com) Message-ID: <4D8BD180.1060600@bsdimp.com> Date: Thu, 24 Mar 2011 17:19:28 -0600 From: Warner Losh User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101211 Thunderbird/3.1.7 MIME-Version: 1.0 To: John Baldwin References: <201103161644.p2GGi8ug098283@svn.freebsd.org> <20110317200156.GB65858@server.vk2pj.dyndns.org> <201103171706.12993.jkim@FreeBSD.org> <201103230834.19151.jhb@freebsd.org> In-Reply-To: <201103230834.19151.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Peter Jeremy , Jung-uk Kim Subject: Re: svn commit: r219700 - head/sys/x86/x86 X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2011 23:26:15 -0000 On 03/23/2011 06:34, John Baldwin wrote: > On Thursday, March 17, 2011 5:06:09 pm Jung-uk Kim wrote: >> On Thursday 17 March 2011 04:01 pm, Peter Jeremy wrote: >>> On 2011-Mar-16 16:44:08 +0000, Jung-uk Kim wrote: >>>> Log: >>>> Revert r219676. >>> Thanks also. For extra kudos, how about adding a similar function >>> to allow the HPET frequency to be over-ridden. That is currently >>> the only timecounter that does not allow the user to compensate for >>> incorrect hardware frequencies. >> I really hate the idea of adjusting timecounter frequency from >> userland. I guess "use ntpd(8)" is not a good answer for some >> people. :-( > Actually, that doesn't work well if your timecounter frequency is off by a > lot. Having the timecounter frequency accurate improves the accuracy of > things like ntpd and ptpd. ntpd requires that the time counter be within 128ppm of true. If the time counter guess is off by more than that, you lose: ntpd won't work. Warner