Re: [9fans] Support for Mac OS X Leopard

["Russ Cox" <rsc@swtch.com>]

>> the right thing to do is to fix timesync to notice
>> such jumps and write them off as suspend/resume
>> instead of assuming that the cpu has gotten *very* slow.
>
> timesync still needs to set the correct time (a system which was
> suspended for, say, 10 hours will live 10 hours in the past). perhaps
> devcons.c:^writebintime should be the one to skip updating the clock
> frequency?

timesync is in charge of figuring out the
correspondence between cpu frequency
and real time.  the kernel does what timesync
says.  instead of the kernel second-guessing
timesync, timesync should just be fixed.

sometimes clock speed *does* vary w.r.t. real time.
if i switch from ac to battery on a laptop,
then timesync helps navigate the change
in cpu frequency.

russ