Messages in this thread |  | | From | "H. Peter Anvin" <> | Subject | Re: rdtsc to mili secs? | Date | 16 Nov 2000 15:09:39 -0800 |
| |
Followup to: <20001116115730.A665@suse.cz> By author: Vojtech Pavlik <vojtech@suse.cz> In newsgroup: linux.dev.kernel > > 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 :(
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |