3 ms·
> If overclockers methods are breaking this promise, then operating systems have very little recourse. I guess the real concern is where does software get its
by wtallis 9y ago
> If overclockers methods are breaking this promise, then operating systems have very little recourse.
I guess the real concern is where does software get its information about the ratio of the TSC's rate to the progression of actual wall time. If it's derived from a constant multiplier of the CPU base clock or something like that, then adjusting the base clock could be quite problematic for benchmarking even if that base clock speed remains constant throughout a benchmark run. On the other hand, if the TSC to wall time ratio is measured using an external clock (like HPET), then most overclocking situations are probably fine (since it's pretty rare to overclock peripheral busses on modern platforms).
And since RDTSC is quite deliberately an unprivileged instruction, it's not just the OS we have to worry about on the software side. But hopefully most application authors that directly use the TSC instead of portable APIs know what they're doing. (I wouldn't bet on it.)
- notaplumber 9y agoThe TSC is periodically recalibrated by operating systems from the some other available timer, like HPET or ACPI PM timer.