On 6/9/2
Currently we can not get actually "hardware" CPU frequency.
For cpuinfo_cur_freq is used to show the "hardware" CPU frequency, I
suppose it can not report cached_freq directly.
And the .get function is optional (in include/linux/cpufreq.h, comment
of get: "should be defined, if possible").
In another hand, users still can get current frequency of the CPU as
determined by the governor and cpufreq core by scaling_cur_freq.
So that I recommand remove cpuinfo_cur_freq support to follow the
declaration of cpufreq.
If we can clarify how to get actually "hardware" CPU frequency, we can
add it back.
the only real way to get hardware frequency is aperf/mperf.
even if you read the MSR back, that does not represent the actual
hardware frequency.... because there's 2 (logical) cpus, and the *actual*
hardware frequency is the maximum of the two, but the MSR only shows
what you asked for. Sort of. Kind of. (minus the system not having to
really return
exactly the same value you asked for)
_______________________________________________
MeeGo-kernel mailing list
MeeGo-kernel@lists.meego.com
http://lists.meego.com/listinfo/meego-kernel
