Alan Cox wrote:
>
> > appropriately.) One could, at least theoretically, make them usable
> > in kernel space only (in user space there is no hope, since you can't
> > know which CPU's TSC you're reading), but these machines seem to be so
> > rare that hardly anyone technical enough to fix it cares.
>
> Im working on making the 'notsc' automatic. Trying to 'fix' it is just plain
> hard work. With the fixed one however we can still use the tsc for udelay
> as we have per cpu loops_per_jiffy data.
>
> This btw is why -ac figures out the bus multiplier on your processors. If they
> dont match then we know tsc wants to be off. Just nobody has written the code
> to disable it across all CPUs yet
>
Yes, there are two cases where we can "fix" it: in the timer interrupt
code, and the loops_per_jiffy stuff.
-hpa
--
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
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/
