From owner-freebsd-acpi@FreeBSD.ORG Sat Jul 5 02:12:15 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 1603D1065684 for ; Sat, 5 Jul 2008 02:12:15 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by mx1.freebsd.org (Postfix) with ESMTP id 8AC0F8FC1B for ; Sat, 5 Jul 2008 02:12:14 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from c220-239-252-11.carlnfd3.nsw.optusnet.com.au (c220-239-252-11.carlnfd3.nsw.optusnet.com.au [220.239.252.11]) by mail09.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m652C96U031779 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Jul 2008 12:12:10 +1000 Date: Sat, 5 Jul 2008 12:12:09 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Nate Lawson In-Reply-To: <486E4DE7.60807@root.org> Message-ID: <20080705120027.G12725@delplex.bde.org> References: <20080702191827.GK1469@uriah.heep.sax.de> <20080703145049.S6189@delplex.bde.org> <486E4DE7.60807@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 02:12:15 -0000 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. >> 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? I forgot to mention another MI problem with cpu_ticker frequency recalibration: its sanity checks don't detect even the enormous transient garbage caused by stopping clocks. Apparently all the clocks used in the sanity checks are stopped too synchronously. Otherwise, the recalibration is very accurate. Bruce