Subject: Re: HEADS UP: timecounters (branch simonb-timecounters) merged into
To: None <>
From: Perry E. Metzger <>
List: current-users
Date: 06/09/2006 14:19:33
Chapman Flack <> writes:
> Alan Barrett wrote:
>> If you had a log of the history of recent CPU speed changes (with old
>> speed, new speed, and timestamp for each change) then it should be
>> possible to do the right arithmetic.  Add a hook to the timecounters
>> framework so that the speedstep code can report "I am now changing the
>> speed from X to Y", and let the timecounters code do the bookkeeping.
> Are there circumstances where a "log" containing only the most recent
> speed change and timestamp would not be sufficient?
> I'm not thinking of any right now, but perhaps someone else can.

Sounds like a reasonable approach, but might I humbly suggest that we
check the way that Linux, Windows and other OSes handle this problem?
Surely we're not the first to confront the issue.