From owner-cvs-all Wed Jul 28 13:34: 5 1999 Delivered-To: cvs-all@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 0B73E1552C; Wed, 28 Jul 1999 13:33:42 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA65420; Wed, 28 Jul 1999 22:32:17 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/apm apm.c apm_setup.s apm_setup.h src/sys/i386/isa clock.c In-reply-to: Your message of "Wed, 28 Jul 1999 13:22:31 PDT." <199907282022.NAA25414@freefall.freebsd.org> Date: Wed, 28 Jul 1999 22:32:16 +0200 Message-ID: <65418.933193936@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk In message <199907282022.NAA25414@freefall.freebsd.org>, Mike Smith writes: > In reality, even this isn't good enough; regardless of whether we support > APM or not, the system may well futz with the CPU's clock speed and throw > the TSC off. We need to stop using it for timekeeping except under > controlled circumstances. I'd rather we stop using if it looks manipulated. I have looked at various ways to improve the calibration of the TSC by spending longer time doing it, this is however not enough to detect a manipulated TSC because the timeouts in the bios may be half and whole hours. It can probably be detected by examining "elapsed wall-clock time" in hardclock, and comparing to hz with some margin for jitter. > Curse the lack of a dependable high-resolution timer. Curse the focus on windows in hardware design... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message