From 8976544271043cdf2d7939ca9210d53e194a6cd5 Mon Sep 17 00:00:00 2001 From: Sebastian Fricke Date: Sat, 18 Apr 2020 11:51:40 +0200 Subject: [PATCH] remove accidental corruptions --- Interrupts/linux-interrupts-2.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Interrupts/linux-interrupts-2.md b/Interrupts/linux-interrupts-2.md index 72bb4ba..3c7d61d 100644 --- a/Interrupts/linux-interrupts-2.md +++ b/Interrupts/linux-interrupts-2.md @@ -1,4 +1,4 @@ -Ineerrupts and Interrupt Handling. Part 2. +Interrupts and Interrupt Handling. Part 2. ================================================================================ Start to dive into interrupt and exceptions handling in the Linux kernel @@ -9,7 +9,7 @@ We saw some theory about interrupts and exception handling in the previous [part If you've read the previous parts, you can remember that the earliest place in the Linux kernel `x86_64` architecture-specific source code which is related to the interrupt is located in the [arch/x86/boot/pm.c](https://github.com/torvalds/linux/blob/16f73eb02d7e1765ccab3d2018e0bd98eb93d973/arch/x86/boot/pm.c) source code file and represents the first setup of the [Interrupt Descriptor Table](http://en.wikipedia.org/wiki/Interrupt_descriptor_table). It occurs right before the transition into the [protected mode](http://en.wikipedia.org/wiki/Protected_mode) in the `go_to_protected_mode` function by the call of the `setup_idt`: ```C -vd more about its implementation in the part about Early interrupt and exception handling)/oid go_to_protected_mode(void) +void go_to_protected_mode(void) { ... setup_idt();