Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
---
formal/dyntickrcu.tex | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/formal/dyntickrcu.tex b/formal/dyntickrcu.tex
index bbbdb18..1c99a0b 100644
--- a/formal/dyntickrcu.tex
+++ b/formal/dyntickrcu.tex
@@ -1098,7 +1098,7 @@ The first step is to convert \co{dyntick_nohz()} to
}
It is important to note that when a group of statements is passed
-to \co{EXECUTE_MAINLINE()}, as in lines~11-14, all
+to \co{EXECUTE_MAINLINE()}, as in lines~12-15, all
statements in that group execute atomically.
\QuickQuiz{}
@@ -1216,7 +1216,7 @@ to model an interrupt handler:
}
The loop from lines~7-48 models up to \co{MAX_DYNTICK_LOOP_IRQ}
-interrupts, with lines~8 and~9 forming the loop condition and line~45
+interrupts, with lines~8 and~9 forming the loop condition and line~46
incrementing the control variable.
Line~10 tells \co{dyntick_nohz()} that an interrupt handler
is running, and line~45 tells \co{dyntick_nohz()} that this
@@ -2046,7 +2046,7 @@ Otherwise, the two functions increment \co{dynticks_nmi}, with
\co{rcu_nmi_enter()} leaving it with an odd value and \co{rcu_nmi_exit()}
leaving it with an even value.
Both functions execute memory barriers between this increment
-and possible RCU read-side critical sections on lines~11 and~21,
+and possible RCU read-side critical sections on lines~10 and~20,
respectively.
\subsubsection{Interrupts From Dynticks-Idle Mode}
--
2.10.0
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
