[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200903021833.46540.denys@visp.net.lb>
Date: Mon, 2 Mar 2009 18:33:46 +0200
From: Denys Fedoryschenko <denys@...p.net.lb>
To: Sitsofe Wheeler <sitsofe@...oo.com>
Cc: Matthew Garrett <mjg@...hat.com>, linux-kernel@...r.kernel.org,
"Rafael J. Wysocki" <rjw@...k.pl>, cpufreq@...r.kernel.org,
davej@...hat.com
Subject: Re: 2.6.28 - 2.6.29-rc6-git5 regression, p4-clockmod/cpufreq probably
On Monday 02 March 2009 18:26:21 Sitsofe Wheeler wrote:
> On Mon, Mar 02, 2009 at 06:15:56PM +0200, Denys Fedoryschenko wrote:
> > 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.
>
> If it's just throttling you want can't you do that via
> /proc/acpi/processor/CPU<N>/throttling ...
CPUFreq infrastructure much more powerful.
-d --min <FREQ>
new minimum CPU frequency the governor may select.
-u --max <FREQ>
new maximum CPU frequency the governor may select.
-g --governor <GOV>
new cpufreq governor.
This things you cannot do over inserting values over ACPI. Sure you can
reinvent the wheel, but why?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists