~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/driver-api/thermal/cpu-idle-cooling.rst

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

Diff markup

Differences between /Documentation/driver-api/thermal/cpu-idle-cooling.rst (Version linux-6.12-rc7) and /Documentation/driver-api/thermal/cpu-idle-cooling.rst (Version linux-5.17.15)


  1 .. SPDX-License-Identifier: GPL-2.0                 1 .. SPDX-License-Identifier: GPL-2.0
  2                                                     2 
  3 ================                                    3 ================
  4 CPU Idle Cooling                                    4 CPU Idle Cooling
  5 ================                                    5 ================
  6                                                     6 
  7 Situation:                                          7 Situation:
  8 ----------                                          8 ----------
  9                                                     9 
 10 Under certain circumstances a SoC can reach a      10 Under certain circumstances a SoC can reach a critical temperature
 11 limit and is unable to stabilize the temperatu     11 limit and is unable to stabilize the temperature around a temperature
 12 control. When the SoC has to stabilize the tem     12 control. When the SoC has to stabilize the temperature, the kernel can
 13 act on a cooling device to mitigate the dissip     13 act on a cooling device to mitigate the dissipated power. When the
 14 critical temperature is reached, a decision mu     14 critical temperature is reached, a decision must be taken to reduce
 15 the temperature, that, in turn impacts perform     15 the temperature, that, in turn impacts performance.
 16                                                    16 
 17 Another situation is when the silicon temperat     17 Another situation is when the silicon temperature continues to
 18 increase even after the dynamic leakage is red     18 increase even after the dynamic leakage is reduced to its minimum by
 19 clock gating the component. This runaway pheno     19 clock gating the component. This runaway phenomenon can continue due
 20 to the static leakage. The only solution is to     20 to the static leakage. The only solution is to power down the
 21 component, thus dropping the dynamic and stati     21 component, thus dropping the dynamic and static leakage that will
 22 allow the component to cool down.                  22 allow the component to cool down.
 23                                                    23 
 24 Last but not least, the system can ask for a s     24 Last but not least, the system can ask for a specific power budget but
 25 because of the OPP density, we can only choose     25 because of the OPP density, we can only choose an OPP with a power
 26 budget lower than the requested one and under-     26 budget lower than the requested one and under-utilize the CPU, thus
 27 losing performance. In other words, one OPP un     27 losing performance. In other words, one OPP under-utilizes the CPU
 28 with a power less than the requested power bud     28 with a power less than the requested power budget and the next OPP
 29 exceeds the power budget. An intermediate OPP      29 exceeds the power budget. An intermediate OPP could have been used if
 30 it were present.                                   30 it were present.
 31                                                    31 
 32 Solutions:                                         32 Solutions:
 33 ----------                                         33 ----------
 34                                                    34 
 35 If we can remove the static and the dynamic le     35 If we can remove the static and the dynamic leakage for a specific
 36 duration in a controlled period, the SoC tempe     36 duration in a controlled period, the SoC temperature will
 37 decrease. Acting on the idle state duration or     37 decrease. Acting on the idle state duration or the idle cycle
 38 injection period, we can mitigate the temperat     38 injection period, we can mitigate the temperature by modulating the
 39 power budget.                                      39 power budget.
 40                                                    40 
 41 The Operating Performance Point (OPP) density      41 The Operating Performance Point (OPP) density has a great influence on
 42 the control precision of cpufreq, however diff     42 the control precision of cpufreq, however different vendors have a
 43 plethora of OPP density, and some have large p     43 plethora of OPP density, and some have large power gap between OPPs,
 44 that will result in loss of performance during     44 that will result in loss of performance during thermal control and
 45 loss of power in other scenarios.                  45 loss of power in other scenarios.
 46                                                    46 
 47 At a specific OPP, we can assume that injectin     47 At a specific OPP, we can assume that injecting idle cycle on all CPUs
 48 belong to the same cluster, with a duration gr     48 belong to the same cluster, with a duration greater than the cluster
 49 idle state target residency, we lead to droppi     49 idle state target residency, we lead to dropping the static and the
 50 dynamic leakage for this period (modulo the en     50 dynamic leakage for this period (modulo the energy needed to enter
 51 this state). So the sustainable power with idl     51 this state). So the sustainable power with idle cycles has a linear
 52 relation with the OPP’s sustainable power an     52 relation with the OPP’s sustainable power and can be computed with a
 53 coefficient similar to::                           53 coefficient similar to::
 54                                                    54 
 55             Power(IdleCycle) = Coef x Power(OP     55             Power(IdleCycle) = Coef x Power(OPP)
 56                                                    56 
 57 Idle Injection:                                    57 Idle Injection:
 58 ---------------                                    58 ---------------
 59                                                    59 
 60 The base concept of the idle injection is to f     60 The base concept of the idle injection is to force the CPU to go to an
 61 idle state for a specified time each control c     61 idle state for a specified time each control cycle, it provides
 62 another way to control CPU power and heat in a     62 another way to control CPU power and heat in addition to
 63 cpufreq. Ideally, if all CPUs belonging to the     63 cpufreq. Ideally, if all CPUs belonging to the same cluster, inject
 64 their idle cycles synchronously, the cluster c     64 their idle cycles synchronously, the cluster can reach its power down
 65 state with a minimum power consumption and red     65 state with a minimum power consumption and reduce the static leakage
 66 to almost zero.  However, these idle cycles in     66 to almost zero.  However, these idle cycles injection will add extra
 67 latencies as the CPUs will have to wakeup from     67 latencies as the CPUs will have to wakeup from a deep sleep state.
 68                                                    68 
 69 We use a fixed duration of idle injection that     69 We use a fixed duration of idle injection that gives an acceptable
 70 performance penalty and a fixed latency. Mitig     70 performance penalty and a fixed latency. Mitigation can be increased
 71 or decreased by modulating the duty cycle of t     71 or decreased by modulating the duty cycle of the idle injection.
 72                                                    72 
 73 ::                                                 73 ::
 74                                                    74 
 75      ^                                             75      ^
 76      |                                             76      |
 77      |                                             77      |
 78      |-------                         -------      78      |-------                         -------
 79      |_______|_______________________|_______|     79      |_______|_______________________|_______|___________
 80                                                    80 
 81      <------>                                      81      <------>
 82        idle  <---------------------->              82        idle  <---------------------->
 83                     running                        83                     running
 84                                                    84 
 85       <----------------------------->              85       <----------------------------->
 86               duty cycle 25%                       86               duty cycle 25%
 87                                                    87 
 88                                                    88 
 89 The implementation of the cooling device bases     89 The implementation of the cooling device bases the number of states on
 90 the duty cycle percentage. When no mitigation      90 the duty cycle percentage. When no mitigation is happening the cooling
 91 device state is zero, meaning the duty cycle i     91 device state is zero, meaning the duty cycle is 0%.
 92                                                    92 
 93 When the mitigation begins, depending on the g     93 When the mitigation begins, depending on the governor's policy, a
 94 starting state is selected. With a fixed idle      94 starting state is selected. With a fixed idle duration and the duty
 95 cycle (aka the cooling device state), the runn     95 cycle (aka the cooling device state), the running duration can be
 96 computed.                                          96 computed.
 97                                                    97 
 98 The governor will change the cooling device st     98 The governor will change the cooling device state thus the duty cycle
 99 and this variation will modulate the cooling e     99 and this variation will modulate the cooling effect.
100                                                   100 
101 ::                                                101 ::
102                                                   102 
103      ^                                            103      ^
104      |                                            104      |
105      |                                            105      |
106      |-------                 -------             106      |-------                 -------
107      |_______|_______________|_______|________    107      |_______|_______________|_______|___________
108                                                   108 
109      <------>                                     109      <------>
110        idle  <-------------->                     110        idle  <-------------->
111                 running                           111                 running
112                                                   112 
113       <--------------------->                     113       <--------------------->
114           duty cycle 33%                          114           duty cycle 33%
115                                                   115 
116                                                   116 
117      ^                                            117      ^
118      |                                            118      |
119      |                                            119      |
120      |-------         -------                     120      |-------         -------
121      |_______|_______|_______|___________         121      |_______|_______|_______|___________
122                                                   122 
123      <------>                                     123      <------>
124        idle  <------>                             124        idle  <------>
125               running                             125               running
126                                                   126 
127       <------------->                             127       <------------->
128        duty cycle 50%                             128        duty cycle 50%
129                                                   129 
130 The idle injection duration value must comply     130 The idle injection duration value must comply with the constraints:
131                                                   131 
132 - It is less than or equal to the latency we t    132 - It is less than or equal to the latency we tolerate when the
133   mitigation begins. It is platform dependent     133   mitigation begins. It is platform dependent and will depend on the
134   user experience, reactivity vs performance t    134   user experience, reactivity vs performance trade off we want. This
135   value should be specified.                      135   value should be specified.
136                                                   136 
137 - It is greater than the idle state’s target    137 - It is greater than the idle state’s target residency we want to go
138   for thermal mitigation, otherwise we end up     138   for thermal mitigation, otherwise we end up consuming more energy.
139                                                   139 
140 Power considerations                              140 Power considerations
141 --------------------                              141 --------------------
142                                                   142 
143 When we reach the thermal trip point, we have     143 When we reach the thermal trip point, we have to sustain a specified
144 power for a specific temperature but at this t    144 power for a specific temperature but at this time we consume::
145                                                   145 
146  Power = Capacitance x Voltage^2 x Frequency x    146  Power = Capacitance x Voltage^2 x Frequency x Utilisation
147                                                   147 
148 ... which is more than the sustainable power (    148 ... which is more than the sustainable power (or there is something
149 wrong in the system setup). The ‘Capacitance    149 wrong in the system setup). The ‘Capacitance’ and ‘Utilisation’ are a
150 fixed value, ‘Voltage’ and the ‘Frequenc    150 fixed value, ‘Voltage’ and the ‘Frequency’ are fixed artificially
151 because we don’t want to change the OPP. We     151 because we don’t want to change the OPP. We can group the
152 ‘Capacitance’ and the ‘Utilisation’ in    152 ‘Capacitance’ and the ‘Utilisation’ into a single term which is the
153 ‘Dynamic Power Coefficient (Cdyn)’ Simplif    153 ‘Dynamic Power Coefficient (Cdyn)’ Simplifying the above, we have::
154                                                   154 
155  Pdyn = Cdyn x Voltage^2 x Frequency              155  Pdyn = Cdyn x Voltage^2 x Frequency
156                                                   156 
157 The power allocator governor will ask us someh    157 The power allocator governor will ask us somehow to reduce our power
158 in order to target the sustainable power defin    158 in order to target the sustainable power defined in the device
159 tree. So with the idle injection mechanism, we    159 tree. So with the idle injection mechanism, we want an average power
160 (Ptarget) resulting in an amount of time runni    160 (Ptarget) resulting in an amount of time running at full power on a
161 specific OPP and idle another amount of time.     161 specific OPP and idle another amount of time. That could be put in a
162 equation::                                        162 equation::
163                                                   163 
164  P(opp)target = ((Trunning x (P(opp)running) +    164  P(opp)target = ((Trunning x (P(opp)running) + (Tidle x P(opp)idle)) /
165                         (Trunning + Tidle)        165                         (Trunning + Tidle)
166                                                   166 
167   ...                                             167   ...
168                                                   168 
169  Tidle = Trunning x ((P(opp)running / P(opp)ta    169  Tidle = Trunning x ((P(opp)running / P(opp)target) - 1)
170                                                   170 
171 At this point if we know the running period fo    171 At this point if we know the running period for the CPU, that gives us
172 the idle injection we need. Alternatively if w    172 the idle injection we need. Alternatively if we have the idle
173 injection duration, we can compute the running    173 injection duration, we can compute the running duration with::
174                                                   174 
175  Trunning = Tidle / ((P(opp)running / P(opp)ta    175  Trunning = Tidle / ((P(opp)running / P(opp)target) - 1)
176                                                   176 
177 Practically, if the running power is less than    177 Practically, if the running power is less than the targeted power, we
178 end up with a negative time value, so obviousl    178 end up with a negative time value, so obviously the equation usage is
179 bound to a power reduction, hence a higher OPP    179 bound to a power reduction, hence a higher OPP is needed to have the
180 running power greater than the targeted power.    180 running power greater than the targeted power.
181                                                   181 
182 However, in this demonstration we ignore three    182 However, in this demonstration we ignore three aspects:
183                                                   183 
184  * The static leakage is not defined here, we     184  * The static leakage is not defined here, we can introduce it in the
185    equation but assuming it will be zero most     185    equation but assuming it will be zero most of the time as it is
186    difficult to get the values from the SoC ve    186    difficult to get the values from the SoC vendors
187                                                   187 
188  * The idle state wake up latency (or entry +     188  * The idle state wake up latency (or entry + exit latency) is not
189    taken into account, it must be added in the    189    taken into account, it must be added in the equation in order to
190    rigorously compute the idle injection          190    rigorously compute the idle injection
191                                                   191 
192  * The injected idle duration must be greater     192  * The injected idle duration must be greater than the idle state
193    target residency, otherwise we end up consu    193    target residency, otherwise we end up consuming more energy and
194    potentially invert the mitigation effect       194    potentially invert the mitigation effect
195                                                   195 
196 So the final equation is::                        196 So the final equation is::
197                                                   197 
198  Trunning = (Tidle - Twakeup ) x                  198  Trunning = (Tidle - Twakeup ) x
199                 (((P(opp)dyn + P(opp)static )     199                 (((P(opp)dyn + P(opp)static ) - P(opp)target) / P(opp)target )
                                                      

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php