[bootlin/training-materials updates] master: Kernel slides: minor improvements (c178e2fb)

[Michael Opdenacker]

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/c178e2fba5a2f92d42d7f7fc5c8ca3de24bfd241

>---------------------------------------------------------------

commit c178e2fba5a2f92d42d7f7fc5c8ca3de24bfd241
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Mon Feb 8 11:51:39 2021 +0100

    Kernel slides: minor improvements
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


>---------------------------------------------------------------

c178e2fba5a2f92d42d7f7fc5c8ca3de24bfd241
 .../kernel-driver-development-concurrency.tex             | 15 +++++++++------
 .../kernel-driver-development-debugging.tex               |  1 +
 2 files changed, 10 insertions(+), 6 deletions(-)

diff --git a/slides/kernel-driver-development-concurrency/kernel-driver-development-concurrency.tex b/slides/kernel-driver-development-concurrency/kernel-driver-development-concurrency.tex
index 83d2d4ad..88b173ec 100644
--- a/slides/kernel-driver-development-concurrency/kernel-driver-development-concurrency.tex
+++ b/slides/kernel-driver-development-concurrency/kernel-driver-development-concurrency.tex
@@ -223,11 +223,11 @@ static unsigned int ulite_tx_empty
 \begin{frame}
   \frametitle{Debugging locking and concurrency issues}
   \begin{itemize}
-  \item From Ingo Molnar and Arjan van de Ven
+  \item Lock debugging: prove locking correctness
     \begin{itemize}
+    \item \kconfig{CONFIG_PROVE_LOCKING}
     \item Adds instrumentation to kernel locking code
-    \item Detect violations of locking rules during system life, such
-      as:
+    \item Detect violations of locking rules during system life, such as:
       \begin{itemize}
       \item Locks acquired in different order (keeps track of locking
         sequences and compares them).
@@ -238,9 +238,12 @@ static unsigned int ulite_tx_empty
       in development.
     \item See \kerneldoctext{locking/lockdep-design.txt} for details
     \end{itemize}
-  \item See also {\em KCSAN}, the Kernel Concurrency SANitizer
-        framework, introduced in Linux 5.8, which can find concurrency issues in your system. See
-        \url{https://lwn.net/Articles/816850/} for details.
+  \item Kernel Concurrency SANitizer framework
+     \begin{itemize}
+     \item \kconfig{CONFIG_KCSAN}, introduced in Linux 5.8.
+     \item Can find concurrency issues in your system.
+     \item See \url{https://lwn.net/Articles/816850/} for details.
+     \end{itemize}
   \end{itemize}
 \end{frame}
 
diff --git a/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex b/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
index 31d1536a..de869538 100644
--- a/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
+++ b/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
@@ -196,6 +196,7 @@ dev_info(&pdev->dev, "in probe\n");
 \begin{frame}
   \frametitle{kgdb - A kernel debugger}
   \begin{itemize}
+  \item \kconfig{CONFIG_KGDB} in {\em Kernel hacking}.
   \item The execution of the kernel is fully controlled by \code{gdb}
     from another machine, connected through a serial line.
   \item Can do almost everything, including inserting breakpoints in