Date: Wed, 13 Oct 1999 19:35:12 -0700 (PDT) From: Matthew Jacob <mjacob@feral.com> To: Bruce Evans <bde@zeta.org.au> Cc: Andrew Gallatin <gallatin@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/alpha clock.c interrupt.c Message-ID: <Pine.BSF.4.10.9910131934270.70146-100000@beppo.feral.com> In-Reply-To: <Pine.BSF.4.10.9910141158300.32868-100000@alphplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Actually, it also turns out that hz varies widely- sometimes it is 1024. Sometimes 1200. It is platform dependent- Drew- what did you do here???? On Thu, 14 Oct 1999, Bruce Evans wrote: > On Wed, 13 Oct 1999, Andrew Gallatin wrote: > > > gallatin 1999/10/13 12:18:30 PDT > > > > Modified files: > > sys/alpha/alpha clock.c interrupt.c > > Log: > > Divide the Alpha's hz of 1024 by 8 to obain a stathz of 128. This > > fixes "nice" on the alpha. > > > > obtained from: NetBSD > > reviewed by: dfr > > This mainly weakens the statclock to hide bugs. The most obvious bug is > that _BSD_CLOCKS_PER_SEC_ was broken on alphas (is 100 but needed to be > 1024 if hz was 1024). It seems to be still broken (is 100 but needs to > be 128 if stathz is 128). However, _BSD_CLOCKS_PER_SEC_ only affects > little-used userland interfaces (e.g, clock(3) and times(3)), so the main > bug must be elsewhere. I think there are scaling bugs in schedcpu(), and > NetBSD has fixed them. These bugs may affect all systems with realstathz > != 100. > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9910131934270.70146-100000>