From: Hongbo Zhang <hongbo.zhang@freescale.com>
To: Zoran Markovic <zoran.markovic@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-pm@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
Eduardo Valentin <eduardo.valentin@ti.com>,
Rob Landley <rob@landley.net>,
Amit Daniel Kachhap <amit.daniel@samsung.com>,
Andrew Morton <akpm@linux-foundation.org>,
Durgadoss R <durgadoss.r@intel.com>,
Christian Daudt <bcm@fixthebug.org>,
James King <james.king@linaro.org>
Subject: Re: [RFC PATCH] thermal: add generic cpu hotplug cooling device
Date: Mon, 23 Sep 2013 19:17:31 +0800 [thread overview]
Message-ID: <5240234B.4070800@freescale.com> (raw)
In-Reply-To: <1379715336-22620-1-git-send-email-zoran.markovic@linaro.org>
On 09/21/2013 06:15 AM, Zoran Markovic wrote:
> This patch implements a generic CPU hotplug cooling device. The
> implementation scales down the number of running CPUs when temperature
> increases through a thermal trip point and prevents booting CPUs
> until thermal conditions are restored. Upon restoration, the action
> of starting up a CPU is left to another entity (e.g. CPU offline
> governor, for which a patch is in the works).
>
> In the past two years, ARM considerably reduced the time required for
> CPUs to boot and shutdown; this time is now measured in microseconds.
> This patch is predominantly intended for ARM big.LITTLE architectures
> where big cores are expected to have a much bigger impact on thermal
> budget than little cores, resulting in fast temperature ramps to a trip
> point, i.e. thermal runaways. Switching off the big core(s) may be one
> of the recovery mechanisms to restore system temperature, but the actual
> strategy is left to the thermal governor.
>
> The assumption is that CPU shutdown/startup is a rare event, so no
> attempt was made to make the code atomic, i.e. the code evidently races
> with CPU hotplug driver. The set_cur_state() function offlines CPUs
> iteratively one at a time, checking the cooling state before each CPU
> shutdown. A hotplug notifier callback validates any CPU boot requests
> against current cooling state and approves/denies accordingly. This
> mechanism guarantees that the desired cooling state could be reached in a
> maximum of d-c iterations, where d and c are the "desired" and "current"
> cooling states expressed in the number of offline CPUs.
>
> Credits to Amit Daniel Kachhap for initial attempt to upstream this feature.
>
> Cc: Zhang Rui<rui.zhang@intel.com>
> Cc: Eduardo Valentin<eduardo.valentin@ti.com>
> Cc: Rob Landley<rob@landley.net>
> Cc: Amit Daniel Kachhap<amit.daniel@samsung.com>
> Cc: Andrew Morton<akpm@linux-foundation.org>
> Cc: Durgadoss R<durgadoss.r@intel.com>
> Cc: Christian Daudt<bcm@fixthebug.org>
> Cc: James King<james.king@linaro.org>
> Signed-off-by: Zoran Markovic<zoran.markovic@linaro.org>
> ---
> Documentation/thermal/cpu-cooling-api.txt | 17 ++
> drivers/thermal/Kconfig | 10 +
> drivers/thermal/Makefile | 1 +
> drivers/thermal/cpu_hotplug.c | 362 +++++++++++++++++++++++++++++
> include/linux/cpuhp_cooling.h | 57 +++++
> 5 files changed, 447 insertions(+)
> create mode 100644 drivers/thermal/cpu_hotplug.c
> create mode 100644 include/linux/cpuhp_cooling.h
Only form my point of view:
I like the name of cpu_hotplug_cooling.c and cpu_hotplug_cooling.h
we already have a cpu_cooling.c, that isn't so exact either because we
have more than one method to cool a CPU, these c and h files should be
renamed to cpu_freq_cooling.c and cpu_freq_cooling.h later.
By the way, some servers with tens of CPUs may need this patch too.
next prev parent reply other threads:[~2013-09-23 11:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 22:15 [RFC PATCH] thermal: add generic cpu hotplug cooling device Zoran Markovic
2013-09-23 11:17 ` Hongbo Zhang [this message]
2013-10-04 22:52 ` Zoran Markovic
2013-11-27 21:56 ` Zoran Markovic
2013-11-29 14:08 ` Eduardo Valentin
2013-12-02 23:05 ` Zoran Markovic
2013-12-09 14:30 ` Eduardo Valentin
2013-12-13 0:01 ` Zoran Markovic
[not found] ` <CAHLCerMCjtXNDRceG2u6kuyTrjV=j6S3mUViVMQJyDAwp_6pgA@mail.gmail.com>
2013-12-16 12:44 ` Eduardo Valentin
2013-12-30 20:48 ` Zoran Markovic
2014-02-01 0:21 ` Zoran Markovic
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=5240234B.4070800@freescale.com \
--to=hongbo.zhang@freescale.com \
--cc=akpm@linux-foundation.org \
--cc=amit.daniel@samsung.com \
--cc=bcm@fixthebug.org \
--cc=durgadoss.r@intel.com \
--cc=eduardo.valentin@ti.com \
--cc=james.king@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rob@landley.net \
--cc=rui.zhang@intel.com \
--cc=zoran.markovic@linaro.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;
as well as URLs for NNTP newsgroup(s).