Re: No Intel Speedstep in 5.1_STABLE ?

[Joel Carnat <joel%carnat.net@localhost>]

Le 25 janv. 2011 à 21:44, Manuel Bouyer a écrit :

> On Tue, Jan 25, 2011 at 08:59:41PM +0100, Joel Carnat wrote:
>> Greetings,
>> 
>> I'm on my way to update my 5.0_STABLE XEN3_DOM0/amd64, from 20090805, to a 
>> 5.1_STABLE from 20110122 :)
>> 
>> I have 5.1_STABLE installed, from -daily, in a VM and untared the full 
>> source sets.
>> I have created a "personal" kernel configuration file named "LUUNA" (it add 
>> SPEEDSTEP and a few other things).
>> 
>> When I build the kernel, I get the following error:
>> identcpu.o: In function `cpu_identify':
>> ../../../../arch/x86/x86/identcpu.c:713: undefined reference to `est_init'
>> 
>> Is it still possible to run speedstep with netbsd/xen dom0 ?
> 
> I don't think it's possible. This is something that should be handled by
> the hypervisor itself.

hum... that's what I meant: speedstep on the dom0.
maybe I wasn't clear.

I digged a bit and I found the following CVS commit that enabled SpeedStep last 
time I tried:
http://mail-index.netbsd.org/source-changes/2009/08/05/msg223683.html

I 've grabbed the rdiff and applied it to my 5.1_STABLE source tree and it 
seems to work :-)
The kernel compiled OK and even booted :p

Here's the dmesg relevant part:
(...)
hypervisor0 at mainbus0: Xen version 3.3
vcpu0 at hypervisor0: Intel 686-class, 2161MHz, id 0x6f6
vcpu0: Enhanced SpeedStep (1388 mV) 2167 MHz
vcpu0: Enhanced SpeedStep frequencies available (MHz): 2167 2000 1833 1667 1500 
1333 1167 1000
debug virtual interrupt using event channel 1
xenbus0 at hypervisor0: Xen Virtual Bus Interface
xencons0 at hypervisor0: Xen Virtual Console Driver
acpi0 at hypervisor0: Intel ACPICA 20080321
acpi0: X/RSDT: OemId <INFINI,NNNN1111,06040000>, AslId < LTP,00000000>
(...)

I also get:
# sysctl machdep                                                               
machdep.tsc_freq = 0
machdep.idle-mechanism = xen
machdep.sleep_state = 0
machdep.est.frequency.target = 1000
machdep.est.frequency.current = 1000
machdep.est.frequency.available = 2167 2000 1833 1667 1500 1333 1167 1000
machdep.xen_timepush_ticks = 5303

Any reasons why the source changes haven't been applied to this branch ?

TIA,
        Jo