From owner-cvs-all@FreeBSD.ORG  Thu Sep 30 19:09:28 2004
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Delivered-To: cvs-all@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id AD61416A4CE; Thu, 30 Sep 2004 19:09:28 +0000 (GMT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1042243D1D; Thu, 30 Sep 2004 19:09:28 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id i8UJ9RkJ048972;
	Thu, 30 Sep 2004 21:09:27 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: Ken Smith <kensmith@FreeBSD.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 30 Sep 2004 14:38:59 -0000."
             <200409301438.i8UEcx89022771@repoman.freebsd.org> 
Date: Thu, 30 Sep 2004 21:09:27 +0200
Message-ID: <48971.1096571367@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: cvs-src@FreeBSD.org
cc: src-committers@FreeBSD.org
cc: cvs-all@FreeBSD.org
Subject: Re: cvs commit: src/sys/sparc64/sparc64 machdep.c 
X-BeenThere: cvs-all@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the entire tree <cvs-all.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-all>
List-Post: <mailto:cvs-all@freebsd.org>
List-Help: <mailto:cvs-all-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Sep 2004 19:09:28 -0000

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.