Revision as of 23:25, 3 May 2010 view source osdev>Thepowersgang slight cleanup ← Older edit		Revision as of 16:39, 6 September 2010 view source osdev>Hangin10 mNo edit summary Newer edit →
Line 57: == Small Kernel Setup == If you want (for specific reason) to have code and data clearly separated (let's say 4 MiB for both, starting at 4 MiB ~~aswell~~as well), just use: <source lang="c"> Line 199: == What is the IDT and is it needed? == As said above, the IDT (Interrupt Descriptor Table) loads much the same way as the GDT and its structure is roughly the same except that it only contains gates and not segments. Each gate gives a full reference to a piece of code (code segment, ~~priviledge~~privilege level and offset to the code in that segment) that is now bound to a number between 0 and 255 (the slot in the IDT). The IDT will be one of the first things to be enabled in your kernel sequence, so that you can catch hardware exceptions, listen to external events, etc. See [[Interrupts for dummies]] for more information about the interrupts of X86 family.

GDT Tutorial: Difference between revisions