[PATCH -perfbook 2/3] cpu, SMPdesign, debugging: Add index markers for "thermal throttling"

Signed-off-by: Akira Yokosawa <[email protected]>
---
 SMPdesign/criteria.tex  | 2 +-
 cpu/overview.tex        | 2 +-
 debugging/debugging.tex | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/SMPdesign/criteria.tex b/SMPdesign/criteria.tex
index 17152a90..2e98174b 100644
--- a/SMPdesign/criteria.tex
+++ b/SMPdesign/criteria.tex
@@ -192,6 +192,6 @@ parallel program.
 }\QuickQuizEnd
 
 It is worth reiterating that contention has many guises, including
-lock contention, memory contention, cache overflow, thermal throttling,
+lock contention, memory contention, cache overflow, \IX{thermal throttling},
 and much else besides.
 This chapter looks primarily at lock and memory contention.
diff --git a/cpu/overview.tex b/cpu/overview.tex
index 715084ed..eedf8491 100644
--- a/cpu/overview.tex
+++ b/cpu/overview.tex
@@ -345,7 +345,7 @@ wall-clock time consumed by that code has actually \emph{increased}.
 \ContributedBy{fig:cpu:Encounters Thermal Throttling}{Melissa Broussard, remixed}
 \end{figure}
 
-Welcome to modern thermal throttling.
+Welcome to modern \IX{thermal throttling}.
 
 If you reduced the number of clock cycles by making more effective
 use of the CPU's functional units, you will have increased the
diff --git a/debugging/debugging.tex b/debugging/debugging.tex
index 832d27b2..0fcf4541 100644
--- a/debugging/debugging.tex
+++ b/debugging/debugging.tex
@@ -2355,7 +2355,7 @@ to creep in, including:
 	Assuming that these sources of interference occur randomly,
 	their effect can be minimized by reducing the number of
 	iterations.
-\item	Thermal throttling can understate scalability because increasing
+\item	\IX{Thermal throttling} can understate scalability because increasing
 	CPU activity increases heat generation, and on systems without
 	adequate cooling (most of them!), this can result in the CPU
 	frequency decreasing as the number of CPUs increases.\footnote{
-- 
2.34.1