From owner-freebsd-acpi@FreeBSD.ORG Tue Feb 8 15:12:04 2005 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C47D16A4D1 for ; Tue, 8 Feb 2005 15:12:04 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C90943D46 for ; Tue, 8 Feb 2005 15:12:02 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by rproxy.gmail.com with SMTP id r35so1007036rna for ; Tue, 08 Feb 2005 07:12:01 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=I3JT2dhteVCzsb3oAH1yIbsVEbhGHqNmrqtG5Ho8/0zF0R8PY+1dmLlGjnTit6WV0CcJbUTHUBjbrDxMwpYpgRTPQvn0REhUWpl+CVZDGapnXV7adfz0tcYtZKUH1b1ctqNNs6/iD/W87Ym4DyP92rAqUHJI7vNNTU6VvDtWqZk= Received: by 10.38.149.78 with SMTP id w78mr244239rnd; Tue, 08 Feb 2005 07:12:01 -0800 (PST) Received: by 10.38.22.22 with HTTP; Tue, 8 Feb 2005 07:12:01 -0800 (PST) Message-ID: <346a8022050208071229742e74@mail.gmail.com> Date: Tue, 8 Feb 2005 10:12:01 -0500 From: Coleman Kane To: Nate Lawson , acpi@freebsd.org, amd64@freebsd.org In-Reply-To: <20050208142310.GA24565@gargantuan.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <42068A5C.1030300@root.org> <20050208142310.GA24565@gargantuan.com> Subject: Re: HEADSUP: cpufreq import complete, acpi_throttling changed X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cokane@cokane.org List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2005 15:12:04 -0000 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 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] > > >