From owner-freebsd-acpi@FreeBSD.ORG Sat Jul 5 17:26:26 2008 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E5821065671 for ; Sat, 5 Jul 2008 17:26:26 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 6744C8FC17 for ; Sat, 5 Jul 2008 17:26:26 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 59950 invoked from network); 5 Jul 2008 17:26:26 -0000 Received: from ppp-71-139-0-34.dsl.snfc21.pacbell.net (HELO ?10.0.5.18?) (nate-mail@71.139.0.34) by root.org with ESMTPA; 5 Jul 2008 17:26:26 -0000 Message-ID: <486FAEBB.7080505@root.org> Date: Sat, 05 Jul 2008 10:26:19 -0700 From: Nate Lawson User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Bruce Evans References: <20080702191827.GK1469@uriah.heep.sax.de> <20080703145049.S6189@delplex.bde.org> <486E4DE7.60807@root.org> <20080705120027.G12725@delplex.bde.org> In-Reply-To: <20080705120027.G12725@delplex.bde.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Joerg Wunsch , freebsd-acpi@FreeBSD.org Subject: Re: HP/Compaq nx6325 clock "jumping around" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2008 17:26:26 -0000 Bruce Evans wrote: > On Fri, 4 Jul 2008, Nate Lawson wrote: > >>> On Wed, 2 Jul 2008, Joerg Wunsch wrote: >>> ... >> Bruce Evans wrote: >>> I know of the following bugs in time on nx6325: >> ... >> >> This reminds me -- the algorithm for estimating the cpu frequency >> needs improvement. You had a patch you sent me that reduced its error >> by a lot. Would you commit it? > > I'm further than ever from committing this, since I'm not set up for svn. > > I never merged this to the kernel. Running it in userland on more SMP > machines shows the expected problems from the CPU not being pinnable in > userland. I used it from the kernel and it worked fine but I was scared off by some questions you had regarding the edge cases where calibration might never complete. >>> dev.cpu.0.freq: 1985 >>> dev.cpu.0.freq_levels: 1985/-1 1736/-1 1488/-1 1240/-1 992/-1 744/-1 >>> 496/-1 248/-1 >>> >>> Once I used some performance/power-reduction config and got a list >>> like yours. >>> >>> 1985 actually gives 1995 MHz. >> >> Your freq estimation patch does better than this. > > Aren't the above frequencies just read from acpi read-only data? Depends on the back-end driver being used. dmesg | grep cpu will reveal it. Some drivers like acpi_perf and est do have their own table. Others like p4tcc and acpi_throttle have to estimate it. -- Nate