All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Cc: cpufreq@vger.kernel.org, linux@dominikbrodowski.net,
	Len Brown <lenb@kernel.org>,
	herrmann.der.user@googlemail.com
Subject: Re: [ANNOUNCE] cpupowerutils - cpufrequtils extended with quite some features
Date: Wed, 23 Mar 2011 11:29:09 +0100	[thread overview]
Message-ID: <201103231129.10249.trenn@suse.de> (raw)
In-Reply-To: <201103111247.00212.trenn@suse.de>

Hi Linus, hi Len,

it would be great to get this tool pulled into:
tools/power/cpupower

All that is needed should be to push (old git history should better
be left out):
wget http://gitorious.org/cpupowerutils/cpupowerutils/archive-
tarball/cpupowerutils cpupowerutils.tar.gz
into tools/power/cpupower
and add to MAINTAINERS file:

CPU POWER MONITORING SUBSYSTEM
M:      Dominik Brodowski <linux@dominikbrodowski.net>
M:      Thomas Renninger <trenn@suse.de>
S:      Maintained
F:      tools/power/cpupower

Could this still show up in 2.6.39?

Thanks,

    Thomas



On Friday, March 11, 2011 12:46:59 PM Thomas Renninger wrote:
> Hi,
> 
...
> What is this tool doing?
> ------------------------
> 
> It provides all features cpufrequtils does.
> It got enhanced with cpuidle and turbo/boost mode (on X86) statistics.
> On AMD the exact amount of supported boost states and their frequencies
> are shown. On Intel only turbo/boost support is shown.
> 
> It got enhanced with a generic HW monitor tool (cpupower monitor).
...
> 
> What next?
> ----------
> 
> After some testing phase it would be great to get this tool
> merged into the kernel git repo under:
> tools/power/cpupower

  parent reply	other threads:[~2011-03-23 10:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 11:46 [ANNOUNCE] cpupowerutils - cpufrequtils extended with quite some features Thomas Renninger
2011-03-11 15:56 ` Corentin Chary
2011-03-11 15:56 ` Corentin Chary
2011-03-11 23:53   ` Thomas Renninger
2011-03-11 23:53   ` Thomas Renninger
2011-03-12  9:59     ` Corentin Chary
2011-03-12  9:59     ` Corentin Chary
2011-03-12  0:18 ` Thomas Renninger
2011-03-12  0:18 ` Thomas Renninger
2011-03-12  4:34 ` Yong Zhang
2011-03-12  4:34 ` Yong Zhang
2011-03-12  4:40   ` Yong Zhang
2011-03-12  4:40   ` Yong Zhang
2011-03-23 10:29 ` Thomas Renninger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-11 11:46 Thomas Renninger

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=201103231129.10249.trenn@suse.de \
    --to=trenn@suse.de \
    --cc=cpufreq@vger.kernel.org \
    --cc=herrmann.der.user@googlemail.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=torvalds@linux-foundation.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 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.