There was work before release which had to be pulled since it changed API which some ports could not handle.
A new approach (adding a different API) is in the works from Scott. However, it is possible there are other bugs in the way the cpus are 'parked'. Or it could simply be bugs in top, which Scott is also addressing. > I know there have been some changes in this area, but this seems like a > remaining bug. > > Run top. Press S to show system processes. Observe idle1 and idle3 (the > hyperthreaded idles) stuck at 100%. With 0:00 time. > > Now if you switch hw.smt=1 the 100% slowly ticks down, but the time > immediately jumps up to many hours. > > Just a peculiarity I noticed. Perhaps there's some way to consolidate special > cases? >
