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 v3 0/7] The power allocator thermal governor
Date: Tue, 3 Jun 2014 11:18:28 +0100 [thread overview]
Message-ID: <1401790715-5630-1-git-send-email-javi.merino@arm.com> (raw)
Hi linux-pm,
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.
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[1]. Patch 2
(thermal: document struct thermal_zone_device and thermal_governor)
has already been submitted to linux-pm[2] and is generic.
[1] https://git.kernel.org/cgit/linux/kernel/git/rostedt/linux-trace.git/commit/?h=for-next&id=4449bf927b61b
db4389393c6fea6837214d1ace7
[2] http://article.gmane.org/gmane.linux.power-management.general/46041
Changes since v2:
- Changed the PI controller into a PID controller
- Added static power to the cpu power model
- tz parameter max_dissipatable_power renamed to sustainable_power
- Register the cpufreq cooling device as part of the
power_cpu_actor registration.
Changes since v1:
- Fixed finding cpufreq cooling devices in cpufreq_frequency_change()
- Replaced the cooling device interface with a separate power actor
API
- Addressed most of Eduardo's comments
- Incorporated ftrace support for bitmask to trace cpumasks
Todo:
- Fix kerneldoc strings
- Use tz->passive
- Use cpufreq_get() to get the frequency of the cpu instead of
using the notifiers.
- Rethink the use of trip points and make it less intrusive
- 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 | 164 ++++++++
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 | 606 ++++++++++++++++++++++++++++++
drivers/thermal/power_actor/power_actor.c | 64 ++++
drivers/thermal/power_actor/power_actor.h | 105 ++++++
drivers/thermal/power_allocator.c | 465 +++++++++++++++++++++++
drivers/thermal/thermal_core.c | 90 ++++-
drivers/thermal/thermal_core.h | 8 +
include/linux/ftrace_event.h | 3 +
include/linux/thermal.h | 62 ++-
include/linux/trace_seq.h | 10 +
include/trace/events/thermal.h | 38 ++
include/trace/events/thermal_governor.h | 37 ++
include/trace/ftrace.h | 57 ++-
kernel/trace/trace_output.c | 41 ++
19 files changed, 1822 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.9.1
next reply other threads:[~2014-06-03 10:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 10:18 Javi Merino [this message]
2014-06-03 10:18 ` [RFC PATCH v3 1/7] tracing: Add __bitmask() macro to trace events to cpumasks and other bitmasks Javi Merino
2014-06-03 10:18 ` [RFC PATCH v3 2/7] thermal: document struct thermal_zone_device and thermal_governor Javi Merino
2014-06-03 10:18 ` [RFC PATCH v3 3/7] thermal: let governors have private data for each thermal zone Javi Merino
2014-06-03 10:18 ` [RFC PATCH v3 4/7] thermal: introduce the Power Actor API Javi Merino
2014-06-11 11:32 ` Eduardo Valentin
2014-06-12 13:45 ` Javi Merino
2014-06-03 10:18 ` [RFC PATCH v3 5/7] thermal: add a basic cpu power actor Javi Merino
2014-06-11 12:05 ` Eduardo Valentin
2014-06-12 14:26 ` Javi Merino
2014-06-13 17:01 ` Javi Merino
2014-06-03 10:18 ` [RFC PATCH v3 6/7] thermal: introduce the Power Allocator governor Javi Merino
2014-06-03 10:18 ` [RFC PATCH v3 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=1401790715-5630-1-git-send-email-javi.merino@arm.com \
--to=javi.merino@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=punit.agrawal@arm.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
all inboxes | Powered by JetHome®