Interrupt Handling

The interrupt subsystem. More...

Namespaces
	Guard
	Synchronizes the kernel with interrupts using the Prologue/Epilogue ModelThe Guard is used to synchronize between "normal" core activities (currently just the text output, later system calls) and interrupt handling routines. For this purpose, Guard has a queue for each CPU, in which gate objects can be added. This is necessary if the critical section is occupied at the time an interrupt occurs, and the epilogue() method cannot be processed immediately. The queued epilogues are processed while leaving the critical section.
	Plugbox
	Object-oriented abstraction of an device interrupt tableThis allows you to specify the device handler for each hardware and software interrupt and processor exception. Each device source is represented by a Gate object. These are located in an array with 256 elements, using the index as the vector number.
	IOAPIC
	Abstraction of the I/O APIC that is used for management of external interrupts.The I/O APIC's Core component is the IO-redirection table. This table is used to configure a flexible mapping between the interrupt number and the external interruption. Entries within this table have a width of 64 bit. For convenience, the union IOAPIC::RedirectionTableEntry should be used for modifying these tables (see ioapic_registers.h for details).
	LAPIC
	Abstracts the local APIC (which is integrated into every CPU core)In modern (x86) PCs, every CPU core has its own Local APIC (LAPIC). The LAPIC is the link between the local CPU core and the I/O APIC (that takes care about external interrupt sources. Interrupt messages received by the LAPIC will be passed to the corresponding CPU core and trigger the interrupt handler on this core.

Classes
class	Gate
	Class of objects that are capable of handling interruptsAll objects to be assigned in Plugbox must be derived from this class. More...
class	Guarded
	A handy interface to protect critical sectionsThis exploits the way how the C++ compiler automatically creates constructor and destructor calls in the code, especially when the scope in which an object was declared is left. More...

Functions
void	interrupt_handler (Core::Interrupt::Vector vector, InterruptContext *context)
	High-Level Interrupt Handling.Main interrupt handling routine of the system. This function is called by the corresponding interrupt_entry_VECTOR function (located in interrupt/handler.asm) with disabled interrupts. More...

Detailed Description

The interrupt subsystem.

The interrupt subsystem of StubBS contains all functionality to accept interrupts from the hardware and process them. In later exercises the interrupts will enable applications to execute core functionality (system calls). The entry point for the interrupt subsystem is the function 'interrupt_entry_VECTOR' (in interrupt/handler.asm).

Function Documentation

interrupt_handler()

void interrupt_handler	(	Core::Interrupt::Vector	vector,
		InterruptContext *	context
	)

High-Level Interrupt Handling.Main interrupt handling routine of the system. This function is called by the corresponding interrupt_entry_VECTOR function (located in interrupt/handler.asm) with disabled interrupts.

Parameters

vector	number of the interrupt
context	Pointer to interrupt context (on stack).