All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Fedoryschenko <denys@visp.net.lb>
To: Matthew Garrett <mjg@redhat.com>
Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
	cpufreq@vger.kernel.org, davej@redhat.com
Subject: Re: 2.6.28 - 2.6.29-rc6-git5 regression, p4-clockmod/cpufreq probably
Date: Mon, 2 Mar 2009 18:15:56 +0200	[thread overview]
Message-ID: <200903021815.56191.denys@visp.net.lb> (raw)
In-Reply-To: <20090302160658.GA32708@srcf.ucam.org>

On Monday 02 March 2009 18:06:59 Matthew Garrett wrote:
> On Mon, Mar 02, 2009 at 05:04:59PM +0200, Denys Fedoryschenko wrote:
> > On 2.6.29-rc6 (git5 tested also) also shown in dmesg as available, but i
> > can't change anything.
>
> That's deliberate. p4-clockmod is for thermal management, not clock
> control (since it doesn't actually do any of that)
I know very well it is just throttling, and not real CPU power management.
At the end it does job.

In my case i used it for testing on "virtual" 113 Mhz video encoding to find 
out bottleneck on ffmpeg and to compare performance with Blackfin.

In another case it helps me to limit current from battery(i have custom power 
supply solution), so battery will lasts longer (on spikes, if it uses full 
CPU power at 900 Mhz, voltage dropping (specially on last "drops of battery 
life), and protection unit disconnecting laptop. Throttling helping to 
prevent this.

Actually i am not asking if it nice or not, just if there is feature which is 
not working.

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 15:04 2.6.28 - 2.6.29-rc6-git5 regression, p4-clockmod/cpufreq probably Denys Fedoryschenko
2009-03-02 16:06 ` Matthew Garrett
2009-03-02 16:15   ` Denys Fedoryschenko [this message]
2009-03-02 16:26     ` Sitsofe Wheeler
2009-03-02 16:33       ` Denys Fedoryschenko
2009-03-02 17:23         ` Sitsofe Wheeler
2009-03-02 18:17           ` Denys Fedoryschenko
2009-03-02 20:34             ` Rafael J. Wysocki

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=200903021815.56191.denys@visp.net.lb \
    --to=denys@visp.net.lb \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=rjw@sisk.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.