Hi!
> > Anyway, this should be solvable by checking for clock change in the
> > timer interrupt. This way we should be able to detect when the clock
> > went weird with a 10 ms accuracy. And compensate for that. It should be
> > possible to keep a 'reasonable' clock running even through the clock
> > changes, where reasonable means constantly growing and as close to real
> > time as 10 ms difference max.
> >
>
> Actually, on machines where RDTSC works correctly, you'd like to use
> that to detect a lost timer interrupt.
>
> It's tough, it really is :(
Well, my patch did not do that but you probably want lost timer
interrupt detection so that you avoid false alarms.
But that means you can no longer detect speed change after 10msec:
going from 150MHz to 300MHz is very similar to one lost timer
interrupt.
Pavel
--
I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
