Bug 73421
Summary: | intel/p_state Does not increase into Turbo Boost states and does not display all governors. i5-3201M | ||
---|---|---|---|
Product: | Power Management | Reporter: | Álvaro Castillo (netsys) |
Component: | cpufreq | Assignee: | cpufreq |
Status: | CLOSED DOCUMENTED | ||
Severity: | high | CC: | aaron.lu, dirk.brandewie, lenb, me |
Priority: | P1 | ||
Hardware: | x86-64 | ||
OS: | Linux | ||
Kernel Version: | 3.13.7-200.fc20.x86_64 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Álvaro Castillo
2014-04-03 00:51:16 UTC
2900 MHz max turbo 4 active cores intel_pstate has an internal governor. If you are using intel_pstate you use its internal governor which has two modes performance which is equivalent to the performance governor and powersave roughly equal to ondemand but is better on power. When a scaling driver with an internal governor is being used powersave and performance are the only options You have a 2.5Ghz processor and are getting 2.9Ghz in both cases which *is* in the turbo range. Yes I am getting 2.90 but does not set 3.1Ghz. For example, In this bug https://bugzilla.kernel.org/show_bug.cgi?id=66581 got problems that does not increases more of 2.8Ghz of kernel when max frecuencies is 3.8Ghz. I don't understand why is not increases into 3.1Ghz.If not Intel should be tell the truth about Turbo boost and frequencies. By other hand, I end compile a kernel over 30 minutes more less. However, my friend does have an Intel Core 2 P8600 takes 10 minutes more less. How is a CPU old with 2 cores can compile a kernel into 10 minutes more less than my new CPU It's new model. I think is a bug. Some users of Gentoo with i5 processors tells me that 5-6 minutes more less should be end compiling a kernel process. :/ The msr-tools package from https://01.org/msr-tools/downloads makes it easy to see what P state is being requested for each core with the command: sudo rdmsr -a 0x199 The requested P state is in the upper eight bits. The P state intel_pstate requests is just that a request in the turbo range, the CPU itself decides what frequency will be used while keeping the processor in it thermal envelop. This command reports: rdmsr -a 0x199 rdmsr: invalid option -- 'a' Usage: rdmsr [options] regno --help -h Print this help --version -V Print current version --hexadecimal -x Hexadecimal output (lower case) --capital-hex -X Hexadecimal output (upper case) --decimal -d Signed decimal output --unsigned -u Unsigned decimal output --octal -o Octal output --c-language -c Format output as a C language constant --zero-pad -0 Output leading zeroes --raw -r Raw binary output --processor # -p Select processor number (default 0) --bitfield h:l -f Output bits [h:l] only msr-tools-1.1.2-8.fc20.x86_64 I don't understand this. How can an Intel Core 2 duo more older than my Intel i5 processor It's passed 3 generations of releases built. Be more powerful than it? Some conclusions: - 1º: Intel is lying. I should as good citizen I am report them for fraud. - 2º: Intel_pstate does not working correctly. (In reply to Álvaro Castillo from comment #4) > This command reports: > > > msr-tools-1.1.2-8.fc20.x86_64 > The current version of msr-tools is v1.3 which the link above points to. > I don't understand this. > > How can an Intel Core 2 duo more older than my Intel i5 processor It's > passed 3 generations of releases built. Be more powerful than it? > Are both systems configured the same? memory, disk, laptop/desktop/server? Are you building with the same .config on both systems? > Some conclusions: > - 1º: Intel is lying. I should as good citizen I am report them for fraud. > - 2º: Intel_pstate does not working correctly. So you are getting the highest turbo frequency available when four cores are active. I fail to see how this is an intel_pstate issue. BTW you got the same results with ondemand. |