From owner-cvs-all Fri Apr 27 8:19:27 2001 Delivered-To: cvs-all@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D628B37B443; Fri, 27 Apr 2001 08:19:14 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA05146; Fri, 27 Apr 2001 11:19:14 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f3RFIiJ47723; Fri, 27 Apr 2001 11:18:44 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15081.36308.59291.649794@grasshopper.cs.duke.edu> Date: Fri, 27 Apr 2001 11:18:44 -0400 (EDT) To: John Baldwin Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/alpha mp_machdep.c In-Reply-To: References: <20010427105814.A47421@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin writes: > > > > Could it be because hz on a rawhide is really 1200, but we still > > divide by 8 to get stathz? Eg, stathz is 150 and 150/128 is roughly 117% > > Yes, that would do it. If that is really the case, then simply adjusting > stathz for the rawhide would fix that easily. I think I had a patch for this once... Ah, yes: Index: sys/alpha/alpha/clock.c =================================================================== RCS file: /home/ncvs/src/sys/alpha/alpha/clock.c,v retrieving revision 1.13 diff -u -r1.13 clock.c --- sys/alpha/alpha/clock.c 2000/01/04 11:30:01 1.13 +++ sys/alpha/alpha/clock.c 2000/01/05 15:03:54 @@ -191,7 +191,7 @@ alpha_timecounter.tc_frequency = freq; init_timecounter(&alpha_timecounter); - stathz = 128; + stathz = hz / 8; platform.clockintr = (void (*) __P((void *))) handleclock; /* I don't remember why I never committed that. > > FWIW, I'd like to see all your clock patches committed. > > Gimme an hour or so. :) I think I'm going to redo the alpha clock stuff > slightly so that platforms will actually set a platform.clockintr() for real > that handles both hardclock and statclock. The default will do what the old > function I modified for SMP does, and on teh 4100 we'll use the current > handler, on teh 2100 we will use one that uses forward_*clock since the clock > is roundrobin, etc. Sounds good. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message