Re: enhanced speed step on AMD64

[christos%astron.com@localhost (Christos Zoulas)]

In article <1274633287.811153.11073.nullmailer%galant.ukfsn.org@localhost>,
Iain Hibbert  <plunky%rya-online.net@localhost> wrote:
>On Sun, 23 May 2010, bch%methodlogic.net@localhost wrote:
>
>> Yup, and none of that works -- I've got a Pentium M with speedstep
>> successfully running, so I'm aware of the interface, etc. Was wondering
>> if something changed in the meantime that I missed... I'll leave this
>> thread out there in the hope that someone can shed some light, or set
>> me on the right path...
>
>reading the code (at arch/x86/x86/est.c) seems to indicate that "boot -x"
>should cause _some_ kind of message to be emitted if the est_init()
>function is called. You could also build a kernel with "options EST_DEBUG"
>which will print more..
>
>Then, the code that calls est_init() (in arch/x86/x86/identcpu.c) shows
>
>#ifdef ENHANCED_SPEEDSTEP
>       if (cpu_feature[1] & CPUID2_EST) {
>               if (rdmsr(MSR_MISC_ENABLE) & (1 << 16))
>                       est_init(cpu_vendor);
>       }
>#endif /* ENHANCED_SPEEDSTEP */
>
>and on my machine, "cpuctl identify 0" shows
>
>  cpu0: features2 0xc1a9<SSE3,MONITOR,VMX,EST,TM2,xTPR,PDCM>
>
>I don't know what MSR_MISC_ENABLE means, perhaps just that the CPU is
>enabled..?

That's not the problem. The EST code really needs to go because
it is ~impossible to figure out the proper thing to do from the MSR's.
It is easier do do with ACPI. I am adding some more printfs and if
you boot with -x you'll see what's going on (we don't support new CPU's).

christos