Date: Thu, 30 Sep 2004 21:09:27 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Ken Smith <kensmith@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/sparc64/sparc64 machdep.c Message-ID: <48971.1096571367@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 30 Sep 2004 14:38:59 -0000." <200409301438.i8UEcx89022771@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200409301438.i8UEcx89022771@repoman.freebsd.org>, Ken Smith writes: >kensmith 2004-09-30 14:38:59 UTC > > FreeBSD src repository > > Modified files: > sys/sparc64/sparc64 machdep.c > Log: > This along with v1.6 of counter.c fixes some timecounter issues on > MP machines (hopefully). CPU timers are OK on UP machines but we > don't keep the timers in sync on MP machines so if the CPU's timer > is chosen as the primary timecounter it's possible for time to > not be monotonically increasing because different CPU's counters > may be used at different times. But the CPU's counters are otherwise > one of the higher quality counters available. So, on UP machines > we'll use a relatively high quality value but on MP machines we'll > use a quality that should prevent the CPU's counters from being chosen. The 'microsecond clock' is present in all suns so we don't leave any machines without timecounters, right ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48971.1096571367>