HEADSUP: cpufreq import complete, acpi_throttling changed

[Coleman Kane]

I have the same problem. Looking through the code, it looks like the
throttling code from acpi_cpu.c basically got moved into acpi_perf.c.


On Tue, 8 Feb 2005 09:23:10 -0500, Michael W. Oliver
<michael at gargantuan.com> wrote:
> On 2005-02-06T13:21:32-0800, Nate Lawson wrote:
> > I've finished the major work of importing cpufreq.  As part of this, the
> > sysctls for acpi throttling have been removed.  The power_profile script
> > has been updated, so you can use performance/economy_cpu_freq= in
> > rc.conf to set AC on/offline cpu frequencies.  The acpi throttling
> > support has been compiled into acpi_perf.ko so load that to get
> > throttling.  Do a sysctl dev.cpu to get an understanding of the cpufreq
> > sysctls.
> 
> Nate,
> 
> Thanks for the hard work on cpufreq!  I am running an AMD64 3400 CPU in
> my lappy, and I don't see any difference in dev.cpu with cpufreq and/or
> acpi_perf loaded.  This is all I have:
> 
> dev.cpu.0.%desc: ACPI CPU (2 Cx states)
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> 
> The above is the same for the following conditions:
> 
>  o cpufreq AND acpi_perf NOT loaded
>  o cpufreq (without acpi_perf) loaded
>  o acpi_perf (without cpufreq) loaded
>  o cpufreq AND acpi_perf loaded
> 
> The acpi_ppc module does continue to work for me, however, yielding the
> following additional OIDs from hw.acpi:
> 
> ----------8<--------------
> # sysctl hw.acpi.cpu
> hw.acpi.cpu.cx_supported: C1/0 C2/80
> hw.acpi.cpu.cx_lowest: C2
> hw.acpi.cpu.cx_usage: 2.36% 97.63%
> 
> # kldload acpi_ppc
> 
> # sysctl hw.acpi.cpu
> hw.acpi.cpu.cx_supported: C1/0 C2/80
> hw.acpi.cpu.cx_lowest: C2
> hw.acpi.cpu.cx_usage: 2.32% 97.67%
> hw.acpi.cpu.px_control: -1
> hw.acpi.cpu.px_highest: 0
> hw.acpi.cpu.px_lowest: 2
> hw.acpi.cpu.px_current: 2
> hw.acpi.cpu.px_supported: 2200 1800 800
> hw.acpi.cpu.px_usage: 3.33% 3.33% 93.33%
> ----------8<--------------
> 
> All the stuff you would normally ask for can be found here:
> 
> http://michael.gargantuan.com/sager_4750v/index.htm#Utility_Command_Output
> 
> Also, I had to build the cpufreq and acpi_perf modules manually, as they
> weren't built automatically.  Maybe they aren't "connected" to the build
> for AMD64?
> 
> Thanks again, great work!
> 
> --
> Mike Oliver
> [see complete headers for contact information]
> 
> 
>