Comment 50 for bug 463940

The reason is the max Hz in all of the kernel and user space tools is the max Hz while all cores are active. Turbo Boost only comes into effect when running un-parallelized code on only a fraction of the cores. So, I've seen my Envy 15 hit 3.0GHz in Windows, using Intel's Turbo Boost utility, but only during single threaded, heavy activity. Otherwise, if it's multithreaded, the system won't go above 1.6GHz, which is the max Hz as far as the Linux system can tell. So there's some catch-up to be played there.

Another hint which leads me to this belief is that PowerTOP doesn't understand how to parse/represent TurboBoost, but the openSolaris version does, they patched it themselves. Running openSolaris, I saw all of the different speeds listed, top to bottom, slowest to fastest, with the last entry changing as demand changed. When I ran the linux version, I see the 931MHz state running at the bottom of the list of speeds, even though the speeds get higher going down the list. Therefor, I "believe" it to be working properly since my speeds vary, fans vary, etc..