From: Thomas Renninger <trenn@suse.de>
To: sfr@canb.auug.org.au
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
Len Brown <lenb@kernel.org>,
"Greg Kroah-Hartman" <gregkh@novell.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Andreas Herrmann <andreas.herrmann3@amd.com>
Subject: [SUBMIT REQUEST] cpupowerutils for linux-next
Date: Mon, 4 Apr 2011 15:10:56 +0200 [thread overview]
Message-ID: <201104041510.56570.trenn@suse.de> (raw)
Hi,
this is about the recently announced cpupowerutils project
based on or say an enhancement of the well know
cpufrequtils project:
http://www.spinics.net/lists/cpufreq/msg02137.html
It's basically cpufrequtils with some cpuidle info additions
and the Intel only turbostat tool merged into it in a way
that it can easily get extended for other HW (and got extended
with some AMD facilities).
As there is tools/power/x86 for some time, it would be very
convenient to get cpupowerutils merged into linux-next (for now)
into the tools/power/cpupower directory:
Most of it is directly based on the cpufreq/cpuidle kernel
subsystem and the output gathered by it should be attached
to any CPU frequency/idle related kernel bug.
Dominik was so kind to add the stuff to his pcmcia git tree
as cpupowerutils branch.
Therefore, this can easily be added by pulling from:
git://git.kernel.org/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git cpupowerutils
Even the MAINTAINERS file got adjusted already (thanks!):
CPU POWER MONITORING SUBSYSTEM
M: Dominik Brodowski <linux@dominikbrodowski.net>
M: Thomas Renninger <trenn@suse.de>
S: Maintained
F: tools/power/cpupower
Stephen: I added lkml, linux-pm lists and kernel people I know
working in this area. Please tell me if you can/will just
pull this or whatever you need to make it happen.
Thanks,
Thomas
next reply other threads:[~2011-04-04 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 13:10 Thomas Renninger [this message]
2011-04-04 14:40 ` [SUBMIT REQUEST] cpupowerutils for linux-next Stephen Rothwell
2011-04-04 14:40 ` Stephen Rothwell
2011-04-04 20:14 ` Thomas Renninger
2011-04-04 20:14 ` Thomas Renninger
2011-04-11 3:57 ` Stephen Rothwell
2011-04-11 3:57 ` Stephen Rothwell
2011-04-11 3:58 ` Stephen Rothwell
2011-04-11 3:58 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2011-04-04 13:10 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=201104041510.56570.trenn@suse.de \
--to=trenn@suse.de \
--cc=andreas.herrmann3@amd.com \
--cc=gregkh@novell.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux@dominikbrodowski.net \
--cc=rjw@sisk.pl \
--cc=sfr@canb.auug.org.au \
/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.