From owner-freebsd-questions@FreeBSD.ORG Thu May 5 19:53:39 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8248816A4CE for ; Thu, 5 May 2005 19:53:39 +0000 (GMT) Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [65.75.192.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA10B43DA0 for ; Thu, 5 May 2005 19:53:38 +0000 (GMT) (envelope-from tedm@toybox.placo.com) Received: from tedwin2k (nat-rtr.freebsd-corp-net-guide.com [65.75.197.130]) j45Js8b63494 for ; Thu, 5 May 2005 12:54:08 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: Date: Thu, 5 May 2005 12:53:38 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <995071073.20050505131333@wanadoo.fr> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 Importance: Normal Subject: RE: Clock running fast X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 19:53:39 -0000 > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Anthony > Atkielski > Sent: Thursday, May 05, 2005 4:14 AM > To: freebsd-questions@freebsd.org > Subject: Re: Clock running fast > > > Ted Mittelstaedt writes: > > > Anthony, you really need to look in the code sometime: > > It takes a very long time to find relevant sections of code, and unless > the author was very conscientious, there are usually few or no > explanatory comments, anyway. > find /usr/src/sys -print |grep "whateveryourlookingfor" can help. > > /usr/src/sys/dev/acpica/acpi_timer.c > > Thanks. > > > * If all tests of the counter succeed, use the ACPI-fast method. If > > * at least one failed, default to using the safe routine, which reads > > * the timer multiple times to get a consistent value before > returning. > > Whatever that means. > TSC, dummy, or i8254, probably depending on the results of other tests. > > /usr/src/sys/i386/isa/clock.c > > /usr/src/sys/i386/i386/tsc.c > > Thanks > > > /* > > * We can not use the TSC if we support APM. Precise timekeeping > > * on an APM'ed machine is at best a fools pursuit, since > > * any and all of the time spent in various SMM code can't > > * be reliably accounted for. Reading the RTC is your only > > * source of reliable time info. The i8254 looses too of course > > * but we need to have some kind of time... > > * We don't know at this point whether APM is going to be used > > * or not, nor when it might be activated. Play it safe. > > */ > > Hmm. I think APM is turned off on my machine, at least that's what > FreeBSD says. The manual for the MB doesn't say anything > about SMI use. > I don't like the idea of a motherboard stealing cycles from my machine; > it sounds way too much like a virus, and a virus built into > the hardware > is the worst nightmare. > It is probably a tossup between the i8254 driver taking cycles to run and an internal kernel counter based off the CPU clock taking cycles to run. Ted > -- > Anthony > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" >