From: Pavel Machek <pavel@ucw.cz>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: edubezval@gmail.com, kevin.wangtao@linaro.org,
leo.yan@linaro.org, vincent.guittot@linaro.org,
amit.kachhap@gmail.com, linux-kernel@vger.kernel.org,
javi.merino@kernel.org, rui.zhang@intel.com,
daniel.thompson@linaro.org, linux-pm@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH V2 5/7] thermal/drivers/cpu_cooling: Add idle cooling device documentation
Date: Wed, 7 Mar 2018 00:19:06 +0100 [thread overview]
Message-ID: <20180306231906.GB28911@amd> (raw)
In-Reply-To: <1519226968-19821-6-git-send-email-daniel.lezcano@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 4470 bytes --]
Hi!
> --- /dev/null
> +++ b/Documentation/thermal/cpu-idle-cooling.txt
> @@ -0,0 +1,165 @@
> +
> +Situation:
> +----------
> +
Can we have some real header here? Also if this is .rst, maybe it
should be marked so?
> +Under certain circumstances, the SoC reaches a temperature exceeding
> +the allocated power budget or the maximum temperature limit. The
I don't understand. Power budget is in W, temperature is in
kelvin. Temperature can't exceed power budget AFAICT.
> +former must be mitigated to stabilize the SoC temperature around the
> +temperature control using the defined cooling devices, the latter
later?
> +catastrophic situation where a radical decision must be taken to
> +reduce the temperature under the critical threshold, that can impact
> +the performances.
performance.
> +Another situation is when the silicon reaches a certain temperature
> +which continues to increase even if the dynamic leakage is reduced to
> +its minimum by clock gating the component. The runaway phenomena will
> +continue with the static leakage and only powering down the component,
> +thus dropping the dynamic and static leakage will allow the component
> +to cool down. This situation is critical.
Critical here, critical there. I have trouble following
it. Theoretically hardware should protect itself, because you don't
want kernel bug to damage your CPU?
> +Last but not least, the system can ask for a specific power budget but
> +because of the OPP density, we can only choose an OPP with a power
> +budget lower than the requested one and underuse the CPU, thus losing
> +performances. In other words, one OPP under uses the CPU with a
performance.
> +lesser than the power budget and the next OPP exceed the power budget,
> +an intermediate OPP could have been used if it were present.
was.
> +Solutions:
> +----------
> +
> +If we can remove the static and the dynamic leakage for a specific
> +duration in a controlled period, the SoC temperature will
> +decrease. Acting at the idle state duration or the idle cycle
"should" decrease? If you are in bad environment..
> +The Operating Performance Point (OPP) density has a great influence on
> +the control precision of cpufreq, however different vendors have a
> +plethora of OPP density, and some have large power gap between OPPs,
> +that will result in loss of performance during thermal control and
> +loss of power in other scenes.
scene seems to be wrong word here.
> +At a specific OPP, we can assume injecting idle cycle on all CPUs,
Extra comma?
> +Idle Injection:
> +---------------
> +
> +The base concept of the idle injection is to force the CPU to go to an
> +idle state for a specified time each control cycle, it provides
> +another way to control CPU power and heat in addition to
> +cpufreq. Ideally, if all CPUs of a cluster inject idle synchronously,
> +this cluster can get into the deepest idle state and achieve minimum
> +power consumption, but that will also increase system response latency
> +if we inject less than cpuidle latency.
I don't understand last sentence.
> +The mitigation begins with a maximum period value which decrease
decreases?
> +more cooling effect is requested. When the period duration is equal
> to
> +the idle duration, then we are in a situation the platform can’t
> +dissipate the heat enough and the mitigation fails. In this case
fast enough?
> +situation is considered critical and there is nothing to do. The idle
Nothing to do? Maybe power the system down?
> +The idle injection duration value must comply with the constraints:
> +
> +- It is lesser or equal to the latency we tolerate when the mitigation
less ... than the latency
> +Minimum period
> +--------------
> +
> +The idle injection duration being fixed, it is obvious the minimum
> +period can’t be lesser than that, otherwise we will be scheduling the
less.
> +Practically, if the running power is lesses than the targeted power,
less.
> +However, in this demonstration we ignore three aspects:
> +
> + * The static leakage is not defined here, we can introduce it in the
> + equation but assuming it will be zero most of the time as it is
, but?
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next parent reply other threads:[~2018-03-06 23:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1519226968-19821-1-git-send-email-daniel.lezcano@linaro.org>
[not found] ` <1519226968-19821-6-git-send-email-daniel.lezcano@linaro.org>
2018-03-06 23:19 ` Pavel Machek [this message]
2018-03-07 11:42 ` [PATCH V2 5/7] thermal/drivers/cpu_cooling: Add idle cooling device documentation Daniel Lezcano
2018-03-08 8:59 ` Pavel Machek
2018-03-08 11:54 ` Daniel Thompson
2018-03-07 17:09 ` [PATCH V2 0/7] CPU cooling device new strategies Eduardo Valentin
2018-03-07 18:57 ` Daniel Lezcano
2018-03-08 12:03 ` Daniel Thompson
2018-03-26 14:30 ` Leo Yan
2018-03-27 9:35 ` Daniel Lezcano
[not found] ` <1519226968-19821-7-git-send-email-daniel.lezcano@linaro.org>
2018-03-27 2:03 ` [PATCH V2 6/7] thermal/drivers/cpu_cooling: Introduce the cpu idle cooling driver Leo Yan
2018-03-27 10:26 ` Daniel Lezcano
2018-03-27 12:28 ` Juri Lelli
2018-03-27 12:31 ` Daniel Lezcano
2018-03-27 13:08 ` Juri Lelli
2018-03-27 3:35 ` Leo Yan
2018-03-27 10:56 ` Daniel Lezcano
[not found] ` <20180223073432.GF26947@vireshk-i7>
[not found] ` <faaf027c-e01c-6801-9a0c-ab7e0ba669a1@linaro.org>
2018-02-26 4:30 ` Viresh Kumar
2018-03-13 19:15 ` Daniel Lezcano
2018-04-04 8:50 ` Daniel Lezcano
2018-04-05 4:49 ` Viresh Kumar
2018-03-27 3:43 ` Leo Yan
2018-03-27 11:10 ` Daniel Lezcano
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=20180306231906.GB28911@amd \
--to=pavel@ucw.cz \
--cc=amit.kachhap@gmail.com \
--cc=corbet@lwn.net \
--cc=daniel.lezcano@linaro.org \
--cc=daniel.thompson@linaro.org \
--cc=edubezval@gmail.com \
--cc=javi.merino@kernel.org \
--cc=kevin.wangtao@linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=vincent.guittot@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).