From owner-freebsd-current Fri Nov 3 08:49:41 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA17622 for current-outgoing; Fri, 3 Nov 1995 08:49:41 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id IAA17609 for <current@FreeBSD.org>; Fri, 3 Nov 1995 08:49:37 -0800 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA05415; Fri, 3 Nov 1995 11:49:13 -0500 Date: Fri, 3 Nov 1995 11:49:13 -0500 From: "Garrett A. Wollman" <wollman@lcs.mit.edu> Message-Id: <9511031649.AA05415@halloran-eldar.lcs.mit.edu> To: Bruce Evans <bde@zeta.org.au> Cc: current@FreeBSD.org Subject: Re: Time problems In-Reply-To: <199511031523.CAA11301@godzilla.zeta.org.au> References: <199511031523.CAA11301@godzilla.zeta.org.au> Sender: owner-current@FreeBSD.org Precedence: bulk <<On Sat, 4 Nov 1995 02:23:25 +1100, Bruce Evans <bde@zeta.org.au> said: > You may have to wait for kernel changes (or write them :-) to use the > Pentium clock unless it is very close to an integral number of MHz. > Another problem with using it is that it breaks tickadj(8). > cpu_thisticklen() ignores the default value of `tick', so tickadj > can't be used to compensate for large errors in `pentium_mhz'. I do not see that this is the case. From kern/kern_clock.c: if (timedelta == 0) { time_update = CPU_THISTICKLEN(tick); } else { time_update = CPU_THISTICKLEN(tick) + tickdelta; timedelta -= tickdelta; } Certainly looks like the correct thing to me. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant