* Mike Galbraith <[email protected]> wrote:
> Or, reset to pristine prior to testing, though that's more lines to
> accomplish the same thing. Either way, or some other way...
>
> If check_tsc_warp() is called after initial boot, and the TSC has in
> the meantime been set (BIOS, user, silicon, elves) to a value lower
> than the last stored/stale value, we blame the TSC. Reset to pristine
> condition after every test.
ok, i prefer this fix a bit more. (we dont want to set last_tsc outside
of the sync_lock - which your initial patch does)
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]