[bootlin/training-materials updates] master: Kernel memory: remove unnecessary slide (cf71f5fd)

Michael Opdenacker michael.opdenacker at bootlin.com
Tue Nov 26 11:27:38 CET 2019

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


commit cf71f5fd4f3cd5a44dab9bd715f6baf4f9081871
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Tue Nov 26 11:27:38 2019 +0100

    Kernel memory: remove unnecessary slide
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


 slides/kernel-device-model/kernel-device-model.tex       |  2 ++
 .../kernel-driver-development-memory.tex                 | 16 ----------------
 .../kernel-driver-development-modules.tex                | 12 +++++++-----
 3 files changed, 9 insertions(+), 21 deletions(-)

diff --git a/slides/kernel-device-model/kernel-device-model.tex b/slides/kernel-device-model/kernel-device-model.tex
index 9a0a9f07..c55b6917 100644
--- a/slides/kernel-device-model/kernel-device-model.tex
+++ b/slides/kernel-device-model/kernel-device-model.tex
@@ -242,6 +242,7 @@ module_exit(usb_rtl8150_exit);
   \frametitle{Probe Method}
+  \item Invoked {\bf for each device} bound to a driver
   \item The \code{probe()} method receives as argument a structure
     describing the device, usually specialized by the bus
     infrastructure (\kstruct{pci_dev}, \kstruct{usb_interface}, etc.)
@@ -338,6 +339,7 @@ Source: \kfile{drivers/net/usb/rtl8150.c}
     \item The kernel source code
     \item The {\em Device Tree}, a hardware description file used on
       some architectures.
+    \item BIOS ACPI tables (x86/PC architecture)
diff --git a/slides/kernel-driver-development-memory/kernel-driver-development-memory.tex b/slides/kernel-driver-development-memory/kernel-driver-development-memory.tex
index dee0e6cb..b340dc53 100644
--- a/slides/kernel-driver-development-memory/kernel-driver-development-memory.tex
+++ b/slides/kernel-driver-development-memory/kernel-driver-development-memory.tex
@@ -91,22 +91,6 @@
-  \frametitle{Back to kernel memory}
-  \begin{itemize}
-  \item Kernel memory allocators (see following slides) allocate
-    physical pages, and kernel allocated memory cannot be swapped out,
-    so no fault handling required for kernel memory.
-  \item Most kernel memory allocation functions also return a kernel
-    virtual address to be used within the kernel space.
-  \item Kernel memory low-level allocator manages pages. This is the
-    finest granularity (usually 4 KB, architecture dependent).
-  \item However, the kernel memory management handles smaller memory
-    allocations through its allocator (see \emph{SLAB allocators}
-    – used by \kfunc{kmalloc}).
-  \end{itemize}
   \frametitle{Allocators in the Kernel}
diff --git a/slides/kernel-driver-development-modules/kernel-driver-development-modules.tex b/slides/kernel-driver-development-modules/kernel-driver-development-modules.tex
index 25074eae..fce3edb1 100644
--- a/slides/kernel-driver-development-modules/kernel-driver-development-modules.tex
+++ b/slides/kernel-driver-development-modules/kernel-driver-development-modules.tex
@@ -119,11 +119,11 @@ MODULE_AUTHOR("William Shakespeare");
     \item Used by kernel developers to identify issues coming from
       proprietary drivers, which they can't do anything about
       (“Tainted” kernel notice in kernel crashes and oopses).
+    \item See \kerneldochtml{admin-guide/tainted-kernels}
+      for details about \code{tainted} flag values.
     \item Useful for users to check that their system is 100\% free
       (for the kernel, check \code{/proc/sys/kernel/tainted}; run
       \code{vrms} to check installed packages)
-    \item See \kerneldochtml{admin-guide/tainted-kernels}
-      for details about \code{tainted} flag values.
   \item Values
@@ -316,9 +316,11 @@ static void __exit hello_exit(void)
-Thanks to Jonathan Corbet for the example!\\
-Source code available on: {\small
+Thanks to Jonathan Corbet for the examples\\
+Source code available on:

More information about the training-materials-updates mailing list