Messages in this thread | | | Date | Sat, 30 Oct 1999 12:14:43 -0400 | From | Chad Miller <> | Subject | Re: Wrong bogomips after plugging in AC power |
| |
On Fri, Oct 29, 1999 at 12:20:32PM -0700, Jeremy Fitzhardinge wrote: > Bogomips calculation is pretty slow and CPU consuming. The basic problem is > that the premise, the CPU always runs at the same rate, is flawed. The > solution is to find some other timebase.
I think Jeremy's on the right track. Processor speed is too fickle[1] and bogomip re-calculation too expensive (and ugly) to keep.
Unfortunately, I don't see a truly portable way to do it. CPUs exist on every machine (presumably!), and RTC doesn't. *sigh*
So, referring to the wrong track, if we accept there's no other timebase method, then we might (and I'm talking out of my hat, here) better control the APM hardware to detect what it intends to do to the system, and adjust our bogomip constant with a multiplier.
If that's not possible for some probably obvious reason, feel free to flame me. - chad
[1] Even Intel's newer chip is labeled to run at six hundred and sixty _seven_ megahertz[2]! If that's not a nod to the Jargon File's ``Great Runes'' entry, I've never seen one.
[2] If you know how to underclock a CPU by that one cycle, mail chris@ surfsouth.com. He's really annoyed.
[3] Self-referential footnote[3]!
-- [insert witty quote here] [insert ASCII-art here]
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |