From: Javi Merino <javi.merino@arm.com>
To: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Punit.Agrawal@arm.com, Javi Merino <javi.merino@arm.com>
Subject: [RFC PATCH v2 0/7] The power allocator thermal governor
Date: Tue, 20 May 2014 15:10:50 +0100 [thread overview]
Message-ID: <1400595057-8585-1-git-send-email-javi.merino@arm.com> (raw)
Hi linux-pm,
This is v2 of the RFC we sent in [1]. The power allocator governor
allocates device power to control temperature. This requires
transforming performance requests into requested power, which we do
with the aid of power models. Patch 5 (thermal: add a basic cpu power
actor) implements a simple power model for cpus. The division of
power between the actors ensures that power is allocated where it is
needed the most, based on the current workload.
[1] http://thread.gmane.org/gmane.linux.power-management.general/45000
Patches 1 and 2 are not proper parts of these series and can be merged
separately. Patch 1 (tracing: Add __bitmask() macro to trace events
to cpumasks and other bitmasks) is already in for-next. Patch 2
(thermal: document struct thermal_zone_device and thermal_governor)
has already been submitted to linux-pm[2] and is generic.
[2] http://article.gmane.org/gmane.linux.power-management.general/45434
Changes since v1:
- Fixed finding cpufreq cooling devices in cpufreq_frequency_change()
- Replaced the reworked cooling device interface with a separate
power actor API
- Addressed most of Eduardo's comments
- Incorporated ftrace support for bitmask to trace cpumasks
Todo:
- Add static power to the cpu power model
- Change the PI controller into a PID controller
- Turn power actors into a device
- Let platforms override the power allocator governor parameters
- Add more tracing and provide scripts to evaluate the proposal.
- Tune it to achieve the temperature stability we are aiming for
Cheers,
Javi & Punit
Javi Merino (6):
thermal: document struct thermal_zone_device and thermal_governor
thermal: let governors have private data for each thermal zone
thermal: introduce the Power Actor API
thermal: add a basic cpu power actor
thermal: introduce the Power Allocator governor
thermal: add trace events to the power allocator governor
Steven Rostedt (Red Hat) (1):
tracing: Add __bitmask() macro to trace events to cpumasks and other
bitmasks
Documentation/thermal/power_actor.txt | 75 +++++
Documentation/thermal/power_allocator.txt | 42 +++
drivers/thermal/Kconfig | 23 ++
drivers/thermal/Makefile | 3 +
drivers/thermal/power_actor/Kconfig | 9 +
drivers/thermal/power_actor/Makefile | 7 +
drivers/thermal/power_actor/cpu_actor.c | 424 +++++++++++++++++++++++++++
drivers/thermal/power_actor/power_actor.c | 66 +++++
drivers/thermal/power_actor/power_actor.h | 86 ++++++
drivers/thermal/power_allocator.c | 452 +++++++++++++++++++++++++++++
drivers/thermal/thermal_core.c | 90 +++++-
drivers/thermal/thermal_core.h | 8 +
include/linux/ftrace_event.h | 3 +
include/linux/thermal.h | 58 +++-
include/linux/trace_seq.h | 10 +
include/trace/events/thermal.h | 38 +++
include/trace/events/thermal_governor.h | 35 +++
include/trace/ftrace.h | 57 +++-
kernel/trace/trace_output.c | 41 +++
19 files changed, 1515 insertions(+), 12 deletions(-)
create mode 100644 Documentation/thermal/power_actor.txt
create mode 100644 Documentation/thermal/power_allocator.txt
create mode 100644 drivers/thermal/power_actor/Kconfig
create mode 100644 drivers/thermal/power_actor/Makefile
create mode 100644 drivers/thermal/power_actor/cpu_actor.c
create mode 100644 drivers/thermal/power_actor/power_actor.c
create mode 100644 drivers/thermal/power_actor/power_actor.h
create mode 100644 drivers/thermal/power_allocator.c
create mode 100644 include/trace/events/thermal.h
create mode 100644 include/trace/events/thermal_governor.h
--
1.7.9.5
next reply other threads:[~2014-05-20 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 14:10 Javi Merino [this message]
2014-05-20 14:10 ` [RFC PATCH v2 1/7] tracing: Add __bitmask() macro to trace events to cpumasks and other bitmasks Javi Merino
2014-05-21 2:07 ` Steven Rostedt
2014-05-21 8:26 ` Javi Merino
2014-05-28 14:25 ` Steven Rostedt
2014-05-20 14:10 ` [RFC PATCH v2 2/7] thermal: document struct thermal_zone_device and thermal_governor Javi Merino
2014-05-20 14:10 ` [RFC PATCH v2 3/7] thermal: let governors have private data for each thermal zone Javi Merino
2014-05-20 14:10 ` [RFC PATCH v2 4/7] thermal: introduce the Power Actor API Javi Merino
2014-05-20 14:10 ` [RFC PATCH v2 5/7] thermal: add a basic cpu power actor Javi Merino
2014-05-20 14:10 ` [RFC PATCH v2 6/7] thermal: introduce the Power Allocator governor Javi Merino
2014-05-20 14:10 ` [RFC PATCH v2 7/7] thermal: add trace events to the power allocator governor Javi Merino
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=1400595057-8585-1-git-send-email-javi.merino@arm.com \
--to=javi.merino@arm.com \
--cc=Punit.Agrawal@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®