Vojtech Pavlik wrote:
>
> Anyway, this proves that there indeed are such notebooks that don't
> change just the duty cycle, but also the clock. And, it also means that
> the kernel should take this into account. While I think it's not very
> likely we can compensate for it (remeasure the TSC speed after every
> APM/ACPI call?), we should at least be able to detect it somehow and
> disable the use of TSC in the case its speed varies.
>
> Or at least issue a warning, like Pavel's kernel does, so that the user
> notices the problem and disables TSC in the kernel config. I suppose
> most users live with this unnoticed and causing problems.
>
It's probably impossible to detect; we probably should provide a no-tsc
kernel flag though.
The no-tsc flag should clear the tsc bit in the capabilities, and also
set the bit in CR4 that disables access to it from user space.
-hpa
-- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot."- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Mar 31 2000 - 21:00:30 EST