From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753262AbZBPSTs (ORCPT ); Mon, 16 Feb 2009 13:19:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751373AbZBPSTl (ORCPT ); Mon, 16 Feb 2009 13:19:41 -0500 Received: from cavan.codon.org.uk ([93.93.128.6]:54392 "EHLO vavatch.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751252AbZBPSTk (ORCPT ); Mon, 16 Feb 2009 13:19:40 -0500 Date: Mon, 16 Feb 2009 18:19:36 +0000 From: Matthew Garrett To: Thomas Renninger Cc: linux-kernel@vger.kernel.org Subject: Re: cpuinfo shows wrong MHz value Message-ID: <20090216181936.GA9831@srcf.ucam.org> References: <200902142217.51655.jplatte@naasa.net> <20090216165008.GA8249@srcf.ucam.org> <200902161913.16021.trenn@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200902161913.16021.trenn@suse.de> User-Agent: Mutt/1.5.12-2006-07-14 X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: mjg59@codon.org.uk X-SA-Exim-Scanned: No (on vavatch.codon.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 16, 2009 at 07:13:15PM +0100, Thomas Renninger wrote: > On Monday 16 February 2009 17:50:08 Matthew Garrett wrote: > > On Mon, Feb 16, 2009 at 02:19:50PM +0000, Thomas Renninger wrote: > > > > > There should be a message when this driver is loaded like: > > > "This driver is broken. Don't use it, don't complain." > > > > Please don't. It's perfectly valid (if dumb) for machines to depend on > > the CPU for passive cooling even if they don't expose any P or T states. > No it's not valid. If the BIOS does not export these, it could be for > a reason. We have to deal with insane BIOSes on a regular basis. > > In that case p4-clockmod is the only code that can manage it. The > > removal of the user-visible cpufreq interface should be a strong enough > > hint that it's not intended for speed control. > AFAIK p4-clockmode is still not synchronized with ACPI throttling? It ought to work fine with any systems using MSR-based throttling. > Anyway, I better do not answer on p4_clockmode complaints anymore and > simply delete them, it's just a waste of time. Feel free. -- Matthew Garrett | mjg59@srcf.ucam.org