public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cpuinfo shows wrong MHz value
Date: Mon, 16 Feb 2009 19:47:19 +0100	[thread overview]
Message-ID: <200902161947.19374.trenn@suse.de> (raw)
In-Reply-To: <20090216181936.GA9831@srcf.ucam.org>

On Monday 16 February 2009 19:19:36 Matthew Garrett wrote:
> 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 this case I will agree with BIOS developers that they have to deal
with insane OS implementations...

> > > 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.

This may come from the fact that throttling via ACPI would only kick in
in emergency temperature case. Exactly then, when throttling should be
used, it won't work. I tried it once and I could easily stall the system
by throttling via ACPI and p4_clockmod.

   Thomas

  reply	other threads:[~2009-02-16 18:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-14 21:17 cpuinfo shows wrong MHz value Joerg Platte
2009-02-14 22:29 ` Frans Pop
2009-02-14 22:38   ` Kasper Sandberg
2009-02-14 22:46     ` Frans Pop
2009-02-14 23:22       ` Joerg Platte
2009-02-15  0:02         ` Frans Pop
2009-02-15  7:00           ` Joerg Platte
2009-02-15  7:11             ` Joerg Platte
2009-02-15 16:41               ` Frans Pop
2009-02-16 14:19                 ` Thomas Renninger
2009-02-16 16:50                   ` Matthew Garrett
2009-02-16 18:13                     ` Thomas Renninger
2009-02-16 18:19                       ` Matthew Garrett
2009-02-16 18:47                         ` Thomas Renninger [this message]
2009-02-16 18:52                         ` Frans Pop
2009-02-16 19:01                           ` Matthew Garrett
2009-02-18 19:54                 ` Joerg Platte
2009-02-18 21:05                   ` Frans Pop
2009-02-19 17:03                     ` Joerg Platte
2009-02-20  2:52                       ` Frans Pop
2009-02-20 18:42                         ` Joerg Platte
2009-02-15 17:43               ` Frans Pop

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200902161947.19374.trenn@suse.de \
    --to=trenn@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox