Re: [PATCH] tsc-disable_B9

[Pavel Machek <pavel@elf.ucw.cz>]

Hi!

> > > But silenty breaking apps and not allowing in any way to apps to learn
> > > if the tsc is returning random or if it's returning something
> > > significant (I understand that's the way you did it in -ac) is a no-way
> > > by default IMHO.
> > 
> > All such apps and libraries are already broken have been silently broken
> > since about 1999 and will continue to be broken. Thats been true since
> > speedstep cpus appeared if not before.
> 
> 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

So those apps are broken. They don't work on pretty common hardware.

NUMA-Q is just another kind of hardware where broken applications
break. What's the problem?

> And following your argument that these apps have been silenty broken
> since 1999, if there's no broken app out there, nobody will ever get the
> instruction fault. If there's any app broken out there we probably like

No. rdtsc is still usefull if you are clever and statistically filter
out. Also rdtsc provides you number of cycles, so if you want to know
how many cycles mov %eax,%ebx takes, you can do that even on
speedstep. Anything that correlates rdtsc to real time is broken, however.

								Pavel
-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org