Jump to content

CPUS=1 really is CPUS=2


moonislune
 Share

8 posts in this topic

Recommended Posts

okay, i can't understand this at all. i ran geekbench in windows with both cores enabled in bios and got a score around 1800. turned off one cores in bios and got a score in windows around 1600. in mac leopard, i am stuck using cpus=1 or kp, so i turned both cores back on in bios and booted with cpus=1. my geekbench in mac is around 1700. i ran both the windows and mac tests multiple times. shouldn't there be a bigger difference if mac can only boot with cpus=1?

Link to comment
Share on other sites

okay, i can't understand this at all. i ran geekbench in windows with both cores enabled in bios and got a score around 1800. turned off one cores in bios and got a score in windows around 1600. in mac leopard, i am stuck using cpus=1 or kp, so i turned both cores back on in bios and booted with cpus=1. my geekbench in mac is around 1700. i ran both the windows and mac tests multiple times. shouldn't there be a bigger difference if mac can only boot with cpus=1?

 

Without know what kind of system you have, I will speculate.

 

The main place where people have an issue with booting with out the cpus=1 flag is with single core CPUs that have hyperthreading (like old P4s and Atoms). The regular OSX kernel lacks proper hyperthreading support (but Voodoo Kernel has it worked out). For these systems you aren't seeing the boost because its not a true dual core, just a hack that makes Windows (which has worse multi-thread performance) seem more responsive.

Link to comment
Share on other sites

regular osx kernel has hyperthreading support. If not how are the new nehalem based mac pros supposed to work?

 

Maybe SL added proper hyperthreading code- I recall that Apple developers were impressed with Voodoo Kernel's implementation of it and planned to add it to the official kernel. I have not put SL on my Acer Aspire One to test.

 

Leopard had what we would call broken HT support- it only worked if things were modified to work with it. For example the Dell Mini 9 community got it working though either a modified bios or a specialty bootloader (I don't know which because I lack one and I don't follow the community that much). I am sure that the Mac Pro does whatever freaky things the Vanilla kernel's hyperthreading engine wanted.

 

But for us hackintoshers unless SL changed things, hyperthreading is broken.

Link to comment
Share on other sites

Thanks poofyhairguy and beto2k7! I was pretty sure that both cores were working as the geekbench (win and mac) and xbench (mac) scores were decent, and it's interesting to hear about hyper threading support in leopard and snow leopard. Also got me excited about continuing to use this tablet. Initially I was just going to leave this T2500 cpu in my tablet PC, but I may look at upgrading the CPU to at7200 or t7600 as it looks like I'd get some benefit by doing so. Again many thanks!

Link to comment
Share on other sites

Maybe SL added proper hyperthreading code- I recall that Apple developers were impressed with Voodoo Kernel's implementation of it and planned to add it to the official kernel. I have not put SL on my Acer Aspire One to test.

I'm typing this right now on my Acer Aspire One running SL, but I was having LOTS of kernel panics unless I put cpus=1 in my Boot.plist file.

 

Would there be any performance gain in getting hyperthreading working properly, maybe with fixes to DSDT

Link to comment
Share on other sites

 Share

×
×
  • Create New...