Re: [PATCH] tsc-disable_B9

[Andrea Arcangeli <andrea@suse.de>]

On Wed, Aug 21, 2002 at 05:25:35PM +0100, Alan Cox wrote:
> > certainly fair enough argument in theory, but in practice you're not
> > going to risk running those apps in a laptop or in general with any
> > power management that will decrease the frequency of the cpu anytime.
> 
> Any PIII with speedstep, any Athlon and PIV.
> 
> > Furthmore the speedstep right now today can crash any laptop that boots
> > at reduced mhz and that switches to higher mhz at runtime, that change
> 
> Actually the reduced loops in the kernel seem to work fine
> 
> > of the tsc frequency simply make udelay run faster, and it'll break
> > drivers easily. I suspect there's even an unfixable race condition in
> > the speedstep hardware since it's not the kernel asking for the change
> 
> Fixed in the -ac tree for the non APM triggered case because we use
> cpufreq code

if the reduced loops is supposed to work fine what was there left to fix?

> 
> > significant info via the tsc to userspace, and there's no way to know
> > that your app isn't breaking because of numa, unless you disable the tsc
> > to userspace.
> 
> And you can test that with notsc. Oh and you might also want the code
> that makes notsc on a tsc only kernel print a warning btw. badtsc lets
> you say "I have a brain cell" notsc lets you select "clueless app
> checking mode"

what's wrong with a sysctl to specify you have a brain cell? I'm not
advocating not to let you specify you have a brain cell, I'm only don't
see why we should assume it when we very know apps will break silenty,
and that it will be not noticeable except with subtle breakage after
some runtime in -ac.

Andrea