Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Sep 2004 22:26:52 +0200
From:      "Poul-Henning Kamp" <phk@phk.freebsd.dk>
To:        Marius Strobl <marius@alchemy.franken.de>
Cc:        cvs-all@freebsd.org
Subject:   Re: cvs commit: src/sys/sparc64/sparc64 machdep.c 
Message-ID:  <50355.1096576012@critter.freebsd.dk>
In-Reply-To: Your message of "Thu, 30 Sep 2004 21:40:21 %2B0200." <20040930214021.A84755@newtrinity.zeist.de> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <20040930214021.A84755@newtrinity.zeist.de>, Marius Strobl writes:

>> Funny you should ask.  Testing the first version of this patch was how
>> we found the bug in counter.c - the machine I booted the test kernel
>> with happened to decide the counter-timer wasn't suitable either due
>> to the bug and it came up with no timecounters.  You should see what
>> happens to a machine that's not keeping time.  :-)

I know :-)

I wrote the code so you wouldn't be in doubt something was wrong.

>> We are drastically low on timecounter-capable devices on sparc64
>> though, it seems the counter-timer and the CPU are about all there
>> is.

We just need one good one, so as long as they have that we're fine.

I thought the 1usec counter were a sparc-architecture thing which
all machines had ?

-- 
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?50355.1096576012>