On Fri, 18 Mar 2011, Kostik Belousov wrote:
On Fri, Mar 18, 2011 at 05:26:53PM +1100, Bruce Evans wrote:
...
- set cputicker() has some design bugs. It assumes that the tick frequency
is the same across all CPUs, but the TSC is per-CPU. I have an old SMP
system with CPUs of different frequency that can demonstrate bugs from
this.
We definitely do not support configurations with different models of
CPUs in SMP, this is what Simmetric is about. Different as in frequency
or stepping.
It worked before this bug was implemented. The TSC wasn't used so the
O/S didn't notice the asymmetric frequencies directly, and the O/S
also didn't care about this indirectly. Now there is even more asymmetry
in core frequencies, with the hardware transiently slowing down or
stopping cores independently, at least for cores in different packages.
Ths O/S probably can't see this directly using TSCs since the technology
that changes the core's frequencies probably comes with invariant TSCs,
and the O/S shouldn't care about this indirectly just like before.
Bruce
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[email protected]"
