[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimFg+uYGbSi=Ci-+_e89TgLkyMB7PAJcnt7mzTc@mail.gmail.com>
Date: Fri, 11 Mar 2011 15:56:01 +0000
From: Corentin Chary <corentin.chary@...il.com>
To: Thomas Renninger <trenn@...e.de>
Cc: linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
linux-pm@...ts.linux-foundation.org, discuss@...swatts.org,
power@...host.org, cpufreq@...r.kernel.org,
linux@...inikbrodowski.net, Mattia Dongili <malattia@...ux.it>,
Len Brown <lenb@...nel.org>, Ingo Molnar <mingo@...e.hu>,
herrmann.der.user@...glemail.com, linux-omap@...r.kernel.org,
dri-devel@...ts.freedesktop.org
Subject: Re: [ANNOUNCE] cpupowerutils - cpufrequtils extended with quite some features
On Fri, Mar 11, 2011 at 11:46 AM, Thomas Renninger <trenn@...e.de> wrote:
> Why is there need for another tool?
> -----------------------------------
>
> CPU power consumption vs performance tuning is not about
> CPU frequency switching anymore for quite some time.
> Deep sleep states, traditional dynamic frequency scaling and
> hidden turbo/boost frequencies are tight close together and
> depend on each other. The first two exist on different architectures
> like PPC, Itanium and ARM the latter only on X86.
> On X86 the APU (CPU+GPU) will only run most efficiently if CPU
> and GPU has proper power management in place.
>
> Users and Developers want to have *one* tool to get an overview what their
> system supports and to monitor and debug CPU power management in detail.
>
> The tool should compile and work on as much architectures as
> possible.
>
Hi Thomas,
Do you think handling really vendor specific "boosts" like EeePC's SHE
is in cpupower scope ?
Still, it would not solve the issue of setting SHE mode in a standard
way, or associating it with a governor.
Thanks,
--
Corentin Chary
http://xf.iksaif.net
--
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