€•¥      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ8/translations/zh_CN/admin-guide/thermal/intel_powerclamp”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ8/translations/zh_TW/admin-guide/thermal/intel_powerclamp”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ8/translations/it_IT/admin-guide/thermal/intel_powerclamp”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ8/translations/ja_JP/admin-guide/thermal/intel_powerclamp”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ8/translations/ko_KR/admin-guide/thermal/intel_powerclamp”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ8/translations/sp_SP/admin-guide/thermal/intel_powerclamp”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒIntel Powerclamp Driver”h]”hŒIntel Powerclamp Driver”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒR/var/lib/git/docbuild/linux/Documentation/admin-guide/thermal/intel_powerclamp.rst”h KubhŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hŒ[By:
- Arjan van de Ven <arjan@linux.intel.com>
- Jacob Pan <jacob.jun.pan@linux.intel.com>
”h]”(hŒterm”“”)”}”(hŒBy:”h]”hŒBy:”…””}”(hhÄhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÂhŸh¶h Khh¾ubhŒ
definition”“”)”}”(hhh]”hŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒ(Arjan van de Ven <arjan@linux.intel.com>”h]”hŒ	paragraph”“”)”}”(hhàh]”(hŒArjan van de Ven <”…””}”(hhähžhhŸNh NubhŒ	reference”“”)”}”(hŒarjan@linux.intel.com”h]”hŒarjan@linux.intel.com”…””}”(hhíhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:arjan@linux.intel.com”uh1hëhhäubhŒ>”…””}”(hhähžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h KhhÞubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜhhÙubhÝ)”}”(hŒ*Jacob Pan <jacob.jun.pan@linux.intel.com>
”h]”hã)”}”(hŒ)Jacob Pan <jacob.jun.pan@linux.intel.com>”h]”(hŒJacob Pan <”…””}”(hj  hžhhŸNh Nubhì)”}”(hŒjacob.jun.pan@linux.intel.com”h]”hŒjacob.jun.pan@linux.intel.com”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ$mailto:jacob.jun.pan@linux.intel.com”uh1hëhj  ubhŒ>”…””}”(hj  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜhhÙubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1h×hŸh¶h KhhÔubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhh¾ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h¼hŸh¶h Khh¹ubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hh£hžhhŸNh NubhŒcomment”“”)”}”(hX  Contents:

(*) Introduction
    - Goals and Objectives

(*) Theory of Operation
    - Idle Injection
    - Calibration

(*) Performance Analysis
    - Effectiveness and Limitations
    - Power vs Performance
    - Scalability
    - Calibration
    - Comparison with Alternative Techniques

(*) Usage and Interfaces
    - Generic Thermal Layer (sysfs)
    - Kernel APIs (TBD)

(*) Module Parameters”h]”hX  Contents:

(*) Introduction
    - Goals and Objectives

(*) Theory of Operation
    - Idle Injection
    - Calibration

(*) Performance Analysis
    - Effectiveness and Limitations
    - Power vs Performance
    - Scalability
    - Calibration
    - Comparison with Alternative Techniques

(*) Usage and Interfaces
    - Generic Thermal Layer (sysfs)
    - Kernel APIs (TBD)

(*) Module Parameters”…””}”hjU  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1jS  hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒINTRODUCTION”h]”hŒINTRODUCTION”…””}”(hjh  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hje  hžhhŸh¶h K ubhã)”}”(hXD  Consider the situation where a systemâ€™s power consumption must be
reduced at runtime, due to power budget, thermal constraint, or noise
level, and where active cooling is not preferred. Software managed
passive power reduction must be performed to prevent the hardware
actions that are designed for catastrophic scenarios.”h]”hXD  Consider the situation where a systemâ€™s power consumption must be
reduced at runtime, due to power budget, thermal constraint, or noise
level, and where active cooling is not preferred. Software managed
passive power reduction must be performed to prevent the hardware
actions that are designed for catastrophic scenarios.”…””}”(hjv  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K"hje  hžhubhã)”}”(hŒ`Currently, P-states, T-states (clock modulation), and CPU offlining
are used for CPU throttling.”h]”hŒ`Currently, P-states, T-states (clock modulation), and CPU offlining
are used for CPU throttling.”…””}”(hj„  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K(hje  hžhubhã)”}”(hXK  On Intel CPUs, C-states provide effective power reduction, but so far
theyâ€™re only used opportunistically, based on workload. With the
development of intel_powerclamp driver, the method of synchronizing
idle injection across all online CPU threads was introduced. The goal
is to achieve forced and controllable C-state residency.”h]”hXK  On Intel CPUs, C-states provide effective power reduction, but so far
theyâ€™re only used opportunistically, based on workload. With the
development of intel_powerclamp driver, the method of synchronizing
idle injection across all online CPU threads was introduced. The goal
is to achieve forced and controllable C-state residency.”…””}”(hj’  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K+hje  hžhubhã)”}”(hŒÂTest/Analysis has been made in the areas of power, performance,
scalability, and user experience. In many cases, clear advantage is
shown over taking the CPU offline or modulating the CPU clock.”h]”hŒÂTest/Analysis has been made in the areas of power, performance,
scalability, and user experience. In many cases, clear advantage is
shown over taking the CPU offline or modulating the CPU clock.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K1hje  hžhubeh}”(h]”Œintroduction”ah ]”h"]”Œintroduction”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K ubh¢)”}”(hhh]”(h§)”}”(hŒTHEORY OF OPERATION”h]”hŒTHEORY OF OPERATION”…””}”(hj¹  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj¶  hžhhŸh¶h K7ubh¢)”}”(hhh]”(h§)”}”(hŒIdle Injection”h]”hŒIdle Injection”…””}”(hjÊ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÇ  hžhhŸh¶h K:ubhã)”}”(hŒ‡On modern Intel processors (Nehalem or later), package level C-state
residency is available in MSRs, thus also available to the kernel.”h]”hŒ‡On modern Intel processors (Nehalem or later), package level C-state
residency is available in MSRs, thus also available to the kernel.”…””}”(hjØ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K<hjÇ  hžhubhã)”}”(hŒThese MSRs are::”h]”hŒThese MSRs are:”…””}”(hjæ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K?hjÇ  hžhubhŒliteral_block”“”)”}”(hŒŸ#define MSR_PKG_C2_RESIDENCY      0x60D
#define MSR_PKG_C3_RESIDENCY      0x3F8
#define MSR_PKG_C6_RESIDENCY      0x3F9
#define MSR_PKG_C7_RESIDENCY      0x3FA”h]”hŒŸ#define MSR_PKG_C2_RESIDENCY      0x60D
#define MSR_PKG_C3_RESIDENCY      0x3F8
#define MSR_PKG_C6_RESIDENCY      0x3F9
#define MSR_PKG_C7_RESIDENCY      0x3FA”…””}”hjö  sbah}”(h]”h ]”h"]”h$]”h&]”jc  jd  uh1jô  hŸh¶h KAhjÇ  hžhubhã)”}”(hX›  If the kernel can also inject idle time to the system, then a
closed-loop control system can be established that manages package
level C-state. The intel_powerclamp driver is conceived as such a
control system, where the target set point is a user-selected idle
ratio (based on power reduction), and the error is the difference
between the actual package level C-state residency ratio and the target idle
ratio.”h]”hX›  If the kernel can also inject idle time to the system, then a
closed-loop control system can be established that manages package
level C-state. The intel_powerclamp driver is conceived as such a
control system, where the target set point is a user-selected idle
ratio (based on power reduction), and the error is the difference
between the actual package level C-state residency ratio and the target idle
ratio.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h KFhjÇ  hžhubhã)”}”(hŒUInjection is controlled by high priority kernel threads, spawned for
each online CPU.”h]”hŒUInjection is controlled by high priority kernel threads, spawned for
each online CPU.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h KNhjÇ  hžhubhã)”}”(hXÔ  These kernel threads, with SCHED_FIFO class, are created to perform
clamping actions of controlled duty ratio and duration. Each per-CPU
thread synchronizes its idle time and duration, based on the rounding
of jiffies, so accumulated errors can be prevented to avoid a jittery
effect. Threads are also bound to the CPU such that they cannot be
migrated, unless the CPU is taken offline. In this case, threads
belong to the offlined CPUs will be terminated immediately.”h]”hXÔ  These kernel threads, with SCHED_FIFO class, are created to perform
clamping actions of controlled duty ratio and duration. Each per-CPU
thread synchronizes its idle time and duration, based on the rounding
of jiffies, so accumulated errors can be prevented to avoid a jittery
effect. Threads are also bound to the CPU such that they cannot be
migrated, unless the CPU is taken offline. In this case, threads
belong to the offlined CPUs will be terminated immediately.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h KQhjÇ  hžhubhã)”}”(hXé  Running as SCHED_FIFO and relatively high priority, also allows such
scheme to work for both preemptible and non-preemptible kernels.
Alignment of idle time around jiffies ensures scalability for HZ
values. This effect can be better visualized using a Perf timechart.
The following diagram shows the behavior of kernel thread
kidle_inject/cpu. During idle injection, it runs monitor/mwait idle
for a given "duration", then relinquishes the CPU to other tasks,
until the next time interval.”h]”hXí  Running as SCHED_FIFO and relatively high priority, also allows such
scheme to work for both preemptible and non-preemptible kernels.
Alignment of idle time around jiffies ensures scalability for HZ
values. This effect can be better visualized using a Perf timechart.
The following diagram shows the behavior of kernel thread
kidle_inject/cpu. During idle injection, it runs monitor/mwait idle
for a given â€œdurationâ€, then relinquishes the CPU to other tasks,
until the next time interval.”…””}”(hj.  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h KYhjÇ  hžhubhã)”}”(hX  The NOHZ schedule tick is disabled during idle time, but interrupts
are not masked. Tests show that the extra wakeups from scheduler tick
have a dramatic impact on the effectiveness of the powerclamp driver
on large scale systems (Westmere system with 80 processors).”h]”hX  The NOHZ schedule tick is disabled during idle time, but interrupts
are not masked. Tests show that the extra wakeups from scheduler tick
have a dramatic impact on the effectiveness of the powerclamp driver
on large scale systems (Westmere system with 80 processors).”…””}”(hj<  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h KbhjÇ  hžhubjõ  )”}”(hX  CPU0
                  ____________          ____________
kidle_inject/0   |   sleep    |  mwait |  sleep     |
        _________|            |________|            |_______
                               duration
CPU1
                  ____________          ____________
kidle_inject/1   |   sleep    |  mwait |  sleep     |
        _________|            |________|            |_______
                              ^
                              |
                              |
                              roundup(jiffies, interval)”h]”hX  CPU0
                  ____________          ____________
kidle_inject/0   |   sleep    |  mwait |  sleep     |
        _________|            |________|            |_______
                               duration
CPU1
                  ____________          ____________
kidle_inject/1   |   sleep    |  mwait |  sleep     |
        _________|            |________|            |_______
                              ^
                              |
                              |
                              roundup(jiffies, interval)”…””}”hjJ  sbah}”(h]”h ]”h"]”h$]”h&]”jc  jd  uh1jô  hŸh¶h KihjÇ  hžhubhã)”}”(hX  Only one CPU is allowed to collect statistics and update global
control parameters. This CPU is referred to as the controlling CPU in
this document. The controlling CPU is elected at runtime, with a
policy that favors BSP, taking into account the possibility of a CPU
hot-plug.”h]”hX  Only one CPU is allowed to collect statistics and update global
control parameters. This CPU is referred to as the controlling CPU in
this document. The controlling CPU is elected at runtime, with a
policy that favors BSP, taking into account the possibility of a CPU
hot-plug.”…””}”(hjX  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h KwhjÇ  hžhubhã)”}”(hXÌ  In terms of dynamics of the idle control system, package level idle
time is considered largely as a non-causal system where its behavior
cannot be based on the past or current input. Therefore, the
intel_powerclamp driver attempts to enforce the desired idle time
instantly as given input (target idle ratio). After injection,
powerclamp monitors the actual idle for a given time window and adjust
the next injection accordingly to avoid over/under correction.”h]”hXÌ  In terms of dynamics of the idle control system, package level idle
time is considered largely as a non-causal system where its behavior
cannot be based on the past or current input. Therefore, the
intel_powerclamp driver attempts to enforce the desired idle time
instantly as given input (target idle ratio). After injection,
powerclamp monitors the actual idle for a given time window and adjust
the next injection accordingly to avoid over/under correction.”…””}”(hjf  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K}hjÇ  hžhubhã)”}”(hXm  When used in a causal control system, such as a temperature control,
it is up to the user of this driver to implement algorithms where
past samples and outputs are included in the feedback. For example, a
PID-based thermal controller can use the powerclamp driver to
maintain a desired target temperature, based on integral and
derivative gains of the past samples.”h]”hXm  When used in a causal control system, such as a temperature control,
it is up to the user of this driver to implement algorithms where
past samples and outputs are included in the feedback. For example, a
PID-based thermal controller can use the powerclamp driver to
maintain a desired target temperature, based on integral and
derivative gains of the past samples.”…””}”(hjt  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K…hjÇ  hžhubeh}”(h]”Œidle-injection”ah ]”h"]”Œidle injection”ah$]”h&]”uh1h¡hj¶  hžhhŸh¶h K:ubh¢)”}”(hhh]”(h§)”}”(hŒCalibration”h]”hŒCalibration”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjŠ  hžhhŸh¶h Kubhã)”}”(hŒÏDuring scalability testing, it is observed that synchronized actions
among CPUs become challenging as the number of cores grows. This is
also true for the ability of a system to enter package level C-states.”h]”hŒÏDuring scalability testing, it is observed that synchronized actions
among CPUs become challenging as the number of cores grows. This is
also true for the ability of a system to enter package level C-states.”…””}”(hj›  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h KhjŠ  hžhubhã)”}”(hŒ„To make sure the intel_powerclamp driver scales well, online
calibration is implemented. The goals for doing such a calibration
are:”h]”hŒ„To make sure the intel_powerclamp driver scales well, online
calibration is implemented. The goals for doing such a calibration
are:”…””}”(hj©  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K”hjŠ  hžhubhŒenumerated_list”“”)”}”(hhh]”(hÝ)”}”(hŒ5determine the effective range of idle injection ratio”h]”hã)”}”(hj¾  h]”hŒ5determine the effective range of idle injection ratio”…””}”(hjÀ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K˜hj¼  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜhj¹  hžhhŸh¶h NubhÝ)”}”(hŒAdetermine the amount of compensation needed at each target ratio
”h]”hã)”}”(hŒ@determine the amount of compensation needed at each target ratio”h]”hŒ@determine the amount of compensation needed at each target ratio”…””}”(hj×  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K™hjÓ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜhj¹  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œ
loweralpha”Œprefix”hŒsuffix”Œ)”uh1j·  hjŠ  hžhhŸh¶h K˜ubhã)”}”(hŒ8Compensation to each target ratio consists of two parts:”h]”hŒ8Compensation to each target ratio consists of two parts:”…””}”(hjö  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K›hjŠ  hžhubhŒblock_quote”“”)”}”(hX`  a) steady state error compensation

   This is to offset the error occurring when the system can
   enter idle without extra wakeups (such as external interrupts).

b) dynamic error compensation

   When an excessive amount of wakeups occurs during idle, an
   additional idle ratio can be added to quiet interrupts, by
   slowing down CPU activities.
”h]”j¸  )”}”(hhh]”(hÝ)”}”(hŒ›steady state error compensation

This is to offset the error occurring when the system can
enter idle without extra wakeups (such as external interrupts).
”h]”(hã)”}”(hŒsteady state error compensation”h]”hŒsteady state error compensation”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h Khj  ubhã)”}”(hŒyThis is to offset the error occurring when the system can
enter idle without extra wakeups (such as external interrupts).”h]”hŒyThis is to offset the error occurring when the system can
enter idle without extra wakeups (such as external interrupts).”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h KŸhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhj
  ubhÝ)”}”(hŒ¯dynamic error compensation

When an excessive amount of wakeups occurs during idle, an
additional idle ratio can be added to quiet interrupts, by
slowing down CPU activities.
”h]”(hã)”}”(hŒdynamic error compensation”h]”hŒdynamic error compensation”…””}”(hj7  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K¢hj3  ubhã)”}”(hŒ’When an excessive amount of wakeups occurs during idle, an
additional idle ratio can be added to quiet interrupts, by
slowing down CPU activities.”h]”hŒ’When an excessive amount of wakeups occurs during idle, an
additional idle ratio can be added to quiet interrupts, by
slowing down CPU activities.”…””}”(hjE  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K¤hj3  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhj
  ubeh}”(h]”h ]”h"]”h$]”h&]”jñ  jò  jó  hjô  jõ  uh1j·  hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh¶h KhjŠ  hžhubhã)”}”(hŒtA debugfs file is provided for the user to examine compensation
progress and results, such as on a Westmere system::”h]”hŒsA debugfs file is provided for the user to examine compensation
progress and results, such as on a Westmere system:”…””}”(hje  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h K¨hjŠ  hžhubjõ  )”}”(hX~  [jacob@nex01 ~]$ cat
/sys/kernel/debug/intel_powerclamp/powerclamp_calib
controlling cpu: 0
pct confidence steady dynamic (compensation)
0       0       0       0
1       1       0       0
2       1       1       0
3       3       1       0
4       3       1       0
5       3       1       0
6       3       1       0
7       3       1       0
8       3       1       0
...
30      3       2       0
31      3       2       0
32      3       1       0
33      3       2       0
34      3       1       0
35      3       2       0
36      3       1       0
37      3       2       0
38      3       1       0
39      3       2       0
40      3       3       0
41      3       1       0
42      3       2       0
43      3       1       0
44      3       1       0
45      3       2       0
46      3       3       0
47      3       0       0
48      3       2       0
49      3       3       0”h]”hX~  [jacob@nex01 ~]$ cat
/sys/kernel/debug/intel_powerclamp/powerclamp_calib
controlling cpu: 0
pct confidence steady dynamic (compensation)
0       0       0       0
1       1       0       0
2       1       1       0
3       3       1       0
4       3       1       0
5       3       1       0
6       3       1       0
7       3       1       0
8       3       1       0
...
30      3       2       0
31      3       2       0
32      3       1       0
33      3       2       0
34      3       1       0
35      3       2       0
36      3       1       0
37      3       2       0
38      3       1       0
39      3       2       0
40      3       3       0
41      3       1       0
42      3       2       0
43      3       1       0
44      3       1       0
45      3       2       0
46      3       3       0
47      3       0       0
48      3       2       0
49      3       3       0”…””}”hjs  sbah}”(h]”h ]”h"]”h$]”h&]”jc  jd  uh1jô  hŸh¶h K«hjŠ  hžhubhã)”}”(hXQ  Calibration occurs during runtime. No offline method is available.
Steady state compensation is used only when confidence levels of all
adjacent ratios have reached satisfactory level. A confidence level
is accumulated based on clean data collected at runtime. Data
collected during a period without extra interrupts is considered
clean.”h]”hXQ  Calibration occurs during runtime. No offline method is available.
Steady state compensation is used only when confidence levels of all
adjacent ratios have reached satisfactory level. A confidence level
is accumulated based on clean data collected at runtime. Data
collected during a period without extra interrupts is considered
clean.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h KÎhjŠ  hžhubhã)”}”(hXˆ  To compensate for excessive amounts of wakeup during idle, additional
idle time is injected when such a condition is detected. Currently,
we have a simple algorithm to double the injection ratio. A possible
enhancement might be to throttle the offending IRQ, such as delaying
EOI for level triggered interrupts. But it is a challenge to be
non-intrusive to the scheduler or the IRQ core code.”h]”hXˆ  To compensate for excessive amounts of wakeup during idle, additional
idle time is injected when such a condition is detected. Currently,
we have a simple algorithm to double the injection ratio. A possible
enhancement might be to throttle the offending IRQ, such as delaying
EOI for level triggered interrupts. But it is a challenge to be
non-intrusive to the scheduler or the IRQ core code.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h KÕhjŠ  hžhubeh}”(h]”Œcalibration”ah ]”h"]”Œcalibration”ah$]”h&]”uh1h¡hj¶  hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒCPU Online/Offline”h]”hŒCPU Online/Offline”…””}”(hj¨  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj¥  hžhhŸh¶h KÞubhã)”}”(hŒíPer-CPU kernel threads are started/stopped upon receiving
notifications of CPU hotplug activities. The intel_powerclamp driver
keeps track of clamping kernel threads, even after they are migrated
to other CPUs, after a CPU offline event.”h]”hŒíPer-CPU kernel threads are started/stopped upon receiving
notifications of CPU hotplug activities. The intel_powerclamp driver
keeps track of clamping kernel threads, even after they are migrated
to other CPUs, after a CPU offline event.”…””}”(hj¶  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h Kßhj¥  hžhubeh}”(h]”Œcpu-online-offline”ah ]”h"]”Œcpu online/offline”ah$]”h&]”uh1h¡hj¶  hžhhŸh¶h KÞubeh}”(h]”Œtheory-of-operation”ah ]”h"]”Œtheory of operation”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K7ubh¢)”}”(hhh]”(h§)”}”(hŒPerformance Analysis”h]”hŒPerformance Analysis”…””}”(hj×  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÔ  hžhhŸh¶h Kæubhã)”}”(hŒ„This section describes the general performance data collected on
multiple systems, including Westmere (80P) and Ivy Bridge (4P, 8P).”h]”hŒ„This section describes the general performance data collected on
multiple systems, including Westmere (80P) and Ivy Bridge (4P, 8P).”…””}”(hjå  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h KçhjÔ  hžhubh¢)”}”(hhh]”(h§)”}”(hŒEffectiveness and Limitations”h]”hŒEffectiveness and Limitations”…””}”(hjö  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjó  hžhhŸh¶h Këubhã)”}”(hXV  The maximum range that idle injection is allowed is capped at 50
percent. As mentioned earlier, since interrupts are allowed during
forced idle time, excessive interrupts could result in less
effectiveness. The extreme case would be doing a ping -f to generated
flooded network interrupts without much CPU acknowledgement. In this
case, little can be done from the idle injection threads. In most
normal cases, such as scp a large file, applications can be throttled
by the powerclamp driver, since slowing down the CPU also slows down
network protocol processing, which in turn reduces interrupts.”h]”hXV  The maximum range that idle injection is allowed is capped at 50
percent. As mentioned earlier, since interrupts are allowed during
forced idle time, excessive interrupts could result in less
effectiveness. The extreme case would be doing a ping -f to generated
flooded network interrupts without much CPU acknowledgement. In this
case, little can be done from the idle injection threads. In most
normal cases, such as scp a large file, applications can be throttled
by the powerclamp driver, since slowing down the CPU also slows down
network protocol processing, which in turn reduces interrupts.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h Kìhjó  hžhubhã)”}”(hX˜  When control parameters change at runtime by the controlling CPU, it
may take an additional period for the rest of the CPUs to catch up
with the changes. During this time, idle injection is out of sync,
thus not able to enter package C- states at the expected ratio. But
this effect is minor, in that in most cases change to the target
ratio is updated much less frequently than the idle injection
frequency.”h]”hX˜  When control parameters change at runtime by the controlling CPU, it
may take an additional period for the rest of the CPUs to catch up
with the changes. During this time, idle injection is out of sync,
thus not able to enter package C- states at the expected ratio. But
this effect is minor, in that in most cases change to the target
ratio is updated much less frequently than the idle injection
frequency.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h Köhjó  hžhubeh}”(h]”Œeffectiveness-and-limitations”ah ]”h"]”Œeffectiveness and limitations”ah$]”h&]”uh1h¡hjÔ  hžhhŸh¶h Këubh¢)”}”(hhh]”(h§)”}”(hŒScalability”h]”hŒScalability”…””}”(hj+  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj(  hžhhŸh¶h Kÿubhã)”}”(hXZ  Tests also show a minor, but measurable, difference between the 4P/8P
Ivy Bridge system and the 80P Westmere server under 50% idle ratio.
More compensation is needed on Westmere for the same amount of
target idle ratio. The compensation also increases as the idle ratio
gets larger. The above reason constitutes the need for the
calibration code.”h]”hXZ  Tests also show a minor, but measurable, difference between the 4P/8P
Ivy Bridge system and the 80P Westmere server under 50% idle ratio.
More compensation is needed on Westmere for the same amount of
target idle ratio. The compensation also increases as the idle ratio
gets larger. The above reason constitutes the need for the
calibration code.”…””}”(hj9  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h M hj(  hžhubhã)”}”(hŒÏOn the IVB 8P system, compared to an offline CPU, powerclamp can
achieve up to 40% better performance per watt. (measured by a spin
counter summed over per CPU counting threads spawned for all running
CPUs).”h]”hŒÏOn the IVB 8P system, compared to an offline CPU, powerclamp can
achieve up to 40% better performance per watt. (measured by a spin
counter summed over per CPU counting threads spawned for all running
CPUs).”…””}”(hjG  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h Mhj(  hžhubeh}”(h]”Œscalability”ah ]”h"]”Œscalability”ah$]”h&]”uh1h¡hjÔ  hžhhŸh¶h Kÿubeh}”(h]”Œperformance-analysis”ah ]”h"]”Œperformance analysis”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kæubh¢)”}”(hhh]”(h§)”}”(hŒUsage and Interfaces”h]”hŒUsage and Interfaces”…””}”(hjh  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hje  hžhhŸh¶h Mubhã)”}”(hŒˆThe powerclamp driver is registered to the generic thermal layer as a
cooling device. Currently, itâ€™s not bound to any thermal zones::”h]”hŒ‡The powerclamp driver is registered to the generic thermal layer as a
cooling device. Currently, itâ€™s not bound to any thermal zones:”…””}”(hjv  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h Mhje  hžhubjõ  )”}”(hŒkjacob@chromoly:/sys/class/thermal/cooling_device14$ grep . *
cur_state:0
max_state:50
type:intel_powerclamp”h]”hŒkjacob@chromoly:/sys/class/thermal/cooling_device14$ grep . *
cur_state:0
max_state:50
type:intel_powerclamp”…””}”hj„  sbah}”(h]”h ]”h"]”h$]”h&]”jc  jd  uh1jô  hŸh¶h Mhje  hžhubhã)”}”(hX  cur_state allows user to set the desired idle percentage. Writing 0 to
cur_state will stop idle injection. Writing a value between 1 and
max_state will start the idle injection. Reading cur_state returns the
actual and current idle percentage. This may not be the same value
set by the user in that current idle percentage depends on workload
and includes natural idle. When idle injection is disabled, reading
cur_state returns value -1 instead of 0 which is to avoid confusing
100% busy state with the disabled state.”h]”hX  cur_state allows user to set the desired idle percentage. Writing 0 to
cur_state will stop idle injection. Writing a value between 1 and
max_state will start the idle injection. Reading cur_state returns the
actual and current idle percentage. This may not be the same value
set by the user in that current idle percentage depends on workload
and includes natural idle. When idle injection is disabled, reading
cur_state returns value -1 instead of 0 which is to avoid confusing
100% busy state with the disabled state.”…””}”(hj’  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h Mhje  hžhubhã)”}”(hŒExample usage:”h]”hŒExample usage:”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h Mhje  hžhubhØ)”}”(hhh]”hÝ)”}”(hŒgTo inject 25% idle time::

      $ sudo sh -c "echo 25 > /sys/class/thermal/cooling_device80/cur_state
”h]”(hã)”}”(hŒTo inject 25% idle time::”h]”hŒTo inject 25% idle time:”…””}”(hjµ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h M!hj±  ubjõ  )”}”(hŒE$ sudo sh -c "echo 25 > /sys/class/thermal/cooling_device80/cur_state”h]”hŒE$ sudo sh -c "echo 25 > /sys/class/thermal/cooling_device80/cur_state”…””}”hjÃ  sbah}”(h]”h ]”h"]”h$]”h&]”jc  jd  uh1jô  hŸh¶h M#hj±  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜhj®  hžhhŸh¶h Nubah}”(h]”h ]”h"]”h$]”h&]”j?  j@  uh1h×hŸh¶h M!hje  hžhubhã)”}”(hŒ³If the system is not busy and has more than 25% idle time already,
then the powerclamp driver will not start idle injection. Using Top
will not show idle injection kernel threads.”h]”hŒ³If the system is not busy and has more than 25% idle time already,
then the powerclamp driver will not start idle injection. Using Top
will not show idle injection kernel threads.”…””}”(hjÝ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h M%hje  hžhubhã)”}”(hŒãIf the system is busy (spin test below) and has less than 25% natural
idle time, powerclamp kernel threads will do idle injection. Forced
idle time is accounted as normal idle in that common code path is
taken as the idle task.”h]”hŒãIf the system is busy (spin test below) and has less than 25% natural
idle time, powerclamp kernel threads will do idle injection. Forced
idle time is accounted as normal idle in that common code path is
taken as the idle task.”…””}”(hjë  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h M)hje  hžhubhã)”}”(hŒ’In this example, 24.1% idle is shown. This helps the system admin or
user determine the cause of slowdown, when a powerclamp driver is in action::”h]”hŒ‘In this example, 24.1% idle is shown. This helps the system admin or
user determine the cause of slowdown, when a powerclamp driver is in action:”…””}”(hjù  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h M.hje  hžhubjõ  )”}”(hX§  Tasks: 197 total,   1 running, 196 sleeping,   0 stopped,   0 zombie
Cpu(s): 71.2%us,  4.7%sy,  0.0%ni, 24.1%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   3943228k total,  1689632k used,  2253596k free,    74960k buffers
Swap:  4087804k total,        0k used,  4087804k free,   945336k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 3352 jacob     20   0  262m  644  428 S  286  0.0   0:17.16 spin
 3341 root     -51   0     0    0    0 D   25  0.0   0:01.62 kidle_inject/0
 3344 root     -51   0     0    0    0 D   25  0.0   0:01.60 kidle_inject/3
 3342 root     -51   0     0    0    0 D   25  0.0   0:01.61 kidle_inject/1
 3343 root     -51   0     0    0    0 D   25  0.0   0:01.60 kidle_inject/2
 2935 jacob     20   0  696m 125m  35m S    5  3.3   0:31.11 firefox
 1546 root      20   0  158m  20m 6640 S    3  0.5   0:26.97 Xorg
 2100 jacob     20   0 1223m  88m  30m S    3  2.3   0:23.68 compiz”h]”hX§  Tasks: 197 total,   1 running, 196 sleeping,   0 stopped,   0 zombie
Cpu(s): 71.2%us,  4.7%sy,  0.0%ni, 24.1%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   3943228k total,  1689632k used,  2253596k free,    74960k buffers
Swap:  4087804k total,        0k used,  4087804k free,   945336k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 3352 jacob     20   0  262m  644  428 S  286  0.0   0:17.16 spin
 3341 root     -51   0     0    0    0 D   25  0.0   0:01.62 kidle_inject/0
 3344 root     -51   0     0    0    0 D   25  0.0   0:01.60 kidle_inject/3
 3342 root     -51   0     0    0    0 D   25  0.0   0:01.61 kidle_inject/1
 3343 root     -51   0     0    0    0 D   25  0.0   0:01.60 kidle_inject/2
 2935 jacob     20   0  696m 125m  35m S    5  3.3   0:31.11 firefox
 1546 root      20   0  158m  20m 6640 S    3  0.5   0:26.97 Xorg
 2100 jacob     20   0 1223m  88m  30m S    3  2.3   0:23.68 compiz”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”jc  jd  uh1jô  hŸh¶h M2hje  hžhubhã)”}”(hX?  Tests have shown that by using the powerclamp driver as a cooling
device, a PID based userspace thermal controller can manage to
control CPU temperature effectively, when no other thermal influence
is added. For example, a UltraBook user can compile the kernel under
certain temperature (below most active trip points).”h]”hX?  Tests have shown that by using the powerclamp driver as a cooling
device, a PID based userspace thermal controller can manage to
control CPU temperature effectively, when no other thermal influence
is added. For example, a UltraBook user can compile the kernel under
certain temperature (below most active trip points).”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h MAhje  hžhubeh}”(h]”Œusage-and-interfaces”ah ]”h"]”Œusage and interfaces”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Mubh¢)”}”(hhh]”(h§)”}”(hŒModule Parameters”h]”hŒModule Parameters”…””}”(hj.  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj+  hžhhŸh¶h MHubh¸)”}”(hhh]”(h½)”}”(hXu  ``cpumask`` (RW)
A bit mask of CPUs to inject idle. The format of the bitmask is same as
used in other subsystems like in /proc/irq/\*/smp_affinity. The mask is
comma separated 32 bit groups. Each CPU is one bit. For example for a 256
CPU system the full mask is:
ffffffff,ffffffff,ffffffff,ffffffff,ffffffff,ffffffff,ffffffff,ffffffff

The rightmost mask is for CPU 0-32.
”h]”(hÃ)”}”(hŒ``cpumask`` (RW)”h]”(hŒliteral”“”)”}”(hŒ``cpumask``”h]”hŒcpumask”…””}”(hjI  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jG  hjC  ubhŒ (RW)”…””}”(hjC  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÂhŸh¶h MQhj?  ubhÓ)”}”(hhh]”(hã)”}”(hX>  A bit mask of CPUs to inject idle. The format of the bitmask is same as
used in other subsystems like in /proc/irq/\*/smp_affinity. The mask is
comma separated 32 bit groups. Each CPU is one bit. For example for a 256
CPU system the full mask is:
ffffffff,ffffffff,ffffffff,ffffffff,ffffffff,ffffffff,ffffffff,ffffffff”h]”hX>  A bit mask of CPUs to inject idle. The format of the bitmask is same as
used in other subsystems like in /proc/irq/ */smp_affinity. The mask is
comma separated 32 bit groups. Each CPU is one bit. For example for a 256
CPU system the full mask is:
ffffffff,ffffffff,ffffffff,ffffffff,ffffffff,ffffffff,ffffffff,ffffffff”…””}”(hjd  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h MKhja  ubhã)”}”(hŒ#The rightmost mask is for CPU 0-32.”h]”hŒ#The rightmost mask is for CPU 0-32.”…””}”(hjr  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h MQhja  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÒhj?  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h¼hŸh¶h MQhj<  ubh½)”}”(hX‡  ``max_idle`` (RW)
Maximum injected idle time to the total CPU time ratio in percent range
from 1 to 100. Even if the cooling device max_state is always 100 (100%),
this parameter allows to add a max idle percent limit. The default is 50,
to match the current implementation of powerclamp driver. Also doesn't
allow value more than 75, if the cpumask includes every CPU present in
the system.”h]”(hÃ)”}”(hŒ``max_idle`` (RW)”h]”(jH  )”}”(hŒ``max_idle``”h]”hŒmax_idle”…””}”(hj”  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jG  hj  ubhŒ (RW)”…””}”(hj  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÂhŸh¶h MXhjŒ  ubhÓ)”}”(hhh]”hã)”}”(hXu  Maximum injected idle time to the total CPU time ratio in percent range
from 1 to 100. Even if the cooling device max_state is always 100 (100%),
this parameter allows to add a max idle percent limit. The default is 50,
to match the current implementation of powerclamp driver. Also doesn't
allow value more than 75, if the cpumask includes every CPU present in
the system.”h]”hXw  Maximum injected idle time to the total CPU time ratio in percent range
from 1 to 100. Even if the cooling device max_state is always 100 (100%),
this parameter allows to add a max idle percent limit. The default is 50,
to match the current implementation of powerclamp driver. Also doesnâ€™t
allow value more than 75, if the cpumask includes every CPU present in
the system.”…””}”(hj¯  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hâhŸh¶h MThj¬  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjŒ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h¼hŸh¶h MXhj<  hžhubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hj+  hžhhŸh¶h Nubeh}”(h]”Œmodule-parameters”ah ]”h"]”Œmodule parameters”ah$]”h&]”uh1h¡hh£hžhhŸh¶h MHubeh}”(h]”Œintel-powerclamp-driver”ah ]”h"]”Œintel powerclamp driver”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jÜ  jÙ  j³  j°  jÑ  jÎ  j‡  j„  j¢  jŸ  jÉ  jÆ  jb  j_  j%  j"  jZ  jW  j(  j%  jÔ  jÑ  uŒ	nametypes”}”(jÜ  ‰j³  ‰jÑ  ‰j‡  ‰j¢  ‰jÉ  ‰jb  ‰j%  ‰jZ  ‰j(  ‰jÔ  ‰uh}”(jÙ  h£j°  je  jÎ  j¶  j„  jÇ  jŸ  jŠ  jÆ  j¥  j_  jÔ  j"  jó  jW  j(  j%  je  jÑ  j+  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.