On 12/6/2012 8:35 AM, Dirk Brandewie wrote:
> would be nice if the new driver can be compatible with the existing > governor by exposing an ability to set and report current frequencies. > But if this is impractical or pointless for Sandy Bridge, so be it. I agree that reporting the current frequency is important to some utilities.
this is a problem btw, for two reasons 1) the answer you get from the sysfs file is only valid for a very very short time (10 msec at most) 2) the answer you get from the sysfs file is a lie... so it's not really valid for even 0.01 msec. Even today, the frequency that is reported is largely fictional, and typically not the frequency of what the core/cpu is actually running it. 10 years ago we could report something reasonable. Hardware just doesn't work that way anymore nowadays... We can report what you ran at (past tense), that is something Intel and AMD hardware exposes. (and if you run powertop, it'll report this as well) But to know what you are currently running at? No chance in hell ;-( -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
