Date: Sat, 7 Jul 2001 21:20:15 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Mike Smith <msmith@FreeBSD.ORG> Cc: Lars Eggert <larse@ISI.EDU>, Peter Pentchev <roam@orbitel.bg>, arch@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: New hw.cpuhz sysctl as per PR i386/27627 Message-ID: <Pine.BSF.4.21.0107072108260.71548-100000@besplex.bde.org> In-Reply-To: <200107062226.f66MQra02267@mass.dis.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 6 Jul 2001, Mike Smith wrote: > > Mike Smith wrote: > > > > > CPU speeds aren't constants; this is probably not the right place to put > > > it. It also assumes there's only one CPU, which isn't acceptable. > > > > Being the author of the original patch, I agree that its a hack - but > > it's better than nothing :-) Plus, it doesn't necessarily assume only > > one CPU - it does assume they all have the same fixed speed though. > > It doesn't seem to serve much useful purpose; the information is already > available to the user in the boot-time message buffer, and it's not > useful as a number to a running process. The same information is already available to the user via the machdep.tsc_freq sysctl if there is a tsc, modulo bugs in the timecounter code (this sysctl is actually only available if there is a tsc AND the tsc timecounter was initialized at boot time). If there is no tsc, then machdep.tsc_freq fails properly but hw.cpuhz bogusly says that the frequency is 0. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" 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.21.0107072108260.71548-100000>