From: Mike Chan <mike@android.com>
To: unlisted-recipients:; (no To-header on input)
Cc: khilman@deeprootsystems.com, menage@google.com,
balbir@in.ibm.com, cpufreq@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
Mike Chan <mike@android.com>
Subject: [PATCH 0/4] Enable cpu frequency and power tracking for cpuacct cgroup
Date: Tue, 18 May 2010 18:30:16 -0700 [thread overview]
Message-ID: <1274232620-23003-1-git-send-email-mike@android.com> (raw)
Rebased onto linux-next.
This patch series introduces cpu frequency and power tracking for cpuacct
cgroups. A similar patch set was discussed a while back and it was concluded
that due to varying architectures (ppc, x86 with overboot) you cannot account
for frequencies and their power consumption generically in sched.c, thus we
have platform specific hooks the cpuacct can call into (if available).
I've implemented all the necessary hooks for OMAP architecture as an example.
For the OMAP folks, I?m not sure what the state of the OPP API in mainline,
as most of my original work was based off of the omap-pm branch.
Mike Chan (4):
scheduler: cpuacct: Enable platform hooks to track cpuusage for CPU
frequencies
omap: cpu: Implement callbacks for cpu frequency tracking in cpuacct
scheduler: cpuacct: Enable platform callbacks for cpuacct power
tracking
omap: cpu: Power tracking support for cgroup cpuacct
Documentation/cgroups/cpuacct.txt | 7 ++
arch/arm/plat-omap/cpu-omap.c | 87 ++++++++++++++++++++++++++++-
arch/arm/plat-omap/include/plat/omap-pm.h | 1 +
include/linux/cpuacct.h | 43 ++++++++++++++
kernel/sched.c | 69 +++++++++++++++++++++++
5 files changed, 206 insertions(+), 1 deletions(-)
create mode 100644 include/linux/cpuacct.h
Signed-off-by: Mike Chan <mike@android.com>
next reply other threads:[~2010-05-19 1:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 1:30 Mike Chan [this message]
2010-05-19 1:30 ` [PATCH 1/4] scheduler: cpuacct: Enable platform hooks to track cpuusage for CPU frequencies Mike Chan
2010-05-19 1:30 ` [PATCH 2/4] omap: cpu: Implement callbacks for cpu frequency tracking in cpuacct Mike Chan
2010-05-19 1:30 ` [PATCH 3/4] scheduler: cpuacct: Enable platform callbacks for cpuacct power tracking Mike Chan
2010-05-19 9:30 ` [PATCH] scheduler: Extract cgroups_cpuaccount code from sched.c into own file Thomas Renninger
2010-05-19 9:37 ` Peter Zijlstra
2010-05-19 10:27 ` Peter Zijlstra
2010-05-19 18:58 ` scheduler: cleanup sched.c and extract cgroup_cpuaccount stuff into separate file Thomas Renninger
2010-05-19 18:58 ` [PATCH 1/2] scheduler: Extract cgroups_cpuaccount code from sched.c into own file V2 Thomas Renninger
2010-05-19 18:58 ` [PATCH 2/2] scheduler: cgroups cpuaccouting: Make cpuusage atomic Thomas Renninger
2010-05-19 19:02 ` Peter Zijlstra
2010-05-19 19:13 ` Thomas Renninger
2010-05-19 19:31 ` Mike Chan
2010-05-20 10:53 ` Thomas Renninger
2010-05-20 0:43 ` KAMEZAWA Hiroyuki
2010-05-19 19:06 ` [PATCH] scheduler: Extract cgroups_cpuaccount code from sched.c into own file Mike Chan
2010-05-19 1:30 ` [PATCH 4/4] omap: cpu: Power tracking support for cgroup cpuacct Mike Chan
2010-05-19 13:11 ` Nishanth Menon
2010-05-19 15:34 ` Thomas Renninger
2010-05-19 18:56 ` Mike Chan
2010-05-19 19:00 ` Nishanth Menon
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=1274232620-23003-1-git-send-email-mike@android.com \
--to=mike@android.com \
--cc=balbir@in.ibm.com \
--cc=cpufreq@vger.kernel.org \
--cc=khilman@deeprootsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=menage@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).