[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1274380944-20947-1-git-send-email-mike@android.com>
Date: Thu, 20 May 2010 11:42:21 -0700
From: Mike Chan <mike@...roid.com>
To: unlisted-recipients:; (no To-header on input)
Cc: menage@...gle.com, balbir@...ibm.com, cpufreq@...r.kernel.org,
linux-kernel@...r.kernel.org, trenn@...e.de,
khilman@...prootsystems.com, linux-omap@...r.kernel.org,
Mike Chan <mike@...roid.com>
Subject: [PATCH v2 0/3] Enable CPU frequency and power tracking in cpuacct cgroup
v2:
Rebased off of Thomas Renninger's patch for cgroups_cpuacct refactoring,
which is based off of linus's tree. Thomas it might be easier to merge our
patches if you take these patches and put them in a series ontop of your
original patches (presuming there are no objections to your patch).
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).
This patch series is not 3 instead of 4. I have left out the power
implementation for OMAP due to implementation conflicts in linux-next.
Mike Chan (3):
scheduler: cpuacct: Enable platform hooks to track cpuusage for CPU
frequencies
scheduler: cpuacct: Enable platform callbacks for cpuacct power
tracking
omap: cpu: Implement callbacks for cpu frequency tracking in cpuacct
Documentation/cgroups/cpuacct.txt | 7 ++++
arch/arm/plat-omap/cpu-omap.c | 67 +++++++++++++++++++++++++++++++++++-
include/linux/cpuacct.h | 43 +++++++++++++++++++++++
kernel/cgroup_cpuaccount.c | 69 +++++++++++++++++++++++++++++++++++++
4 files changed, 185 insertions(+), 1 deletions(-)
create mode 100644 include/linux/cpuacct.h
Signed-off-by: Mike Chan <mike@...roid.com>
--
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