[FE training-materials-updates] [git/training-materials] master: Kernel concurrency: hardware is a shared resource too (acda834)

Michael Opdenacker michael.opdenacker at free-electrons.com
Fri Dec 9 00:10:28 CET 2016


Repository : git://git.free-electrons.com/training-materials.git
On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=acda8342e47deed0af51fd7a93eb92d987858b29

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

commit acda8342e47deed0af51fd7a93eb92d987858b29
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Dec 8 23:10:26 2016 +0100

    Kernel concurrency: hardware is a shared resource too
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

acda8342e47deed0af51fd7a93eb92d987858b29
 .../kernel-driver-development-concurrency.tex                        | 5 +++--
 1 file changed, 3 insertions(+), 2 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 421f934..4298575 100644
--- a/slides/kernel-driver-development-concurrency/kernel-driver-development-concurrency.tex
+++ b/slides/kernel-driver-development-concurrency/kernel-driver-development-concurrency.tex
@@ -10,7 +10,7 @@
     \begin{itemize}
     \item \emph{Interrupts}, which interrupts the current thread to
       execute an interrupt handler. They may be using shared
-      resources.
+      resources (memory addresses, hardware registers...)
     \item \emph{Kernel preemption}, if enabled, causes the kernel to
       switch from the execution of one system call to another. They
       may be using shared resources.
@@ -19,7 +19,8 @@
       using shared resources as well.
     \end{itemize}
   \item The solution is to keep as much local state as possible and
-    for the shared resources, use locking.
+    for the shared resources that can't be made local (such as
+    hardware ones), use locking.
   \end{itemize}
 \end{frame}
 




More information about the training-materials-updates mailing list