mirror of
https://github.com/oliverschmidt/contiki.git
synced 2024-12-22 10:30:13 +00:00
e28f400e0c
This patch introduces the interrupt.h header file which provides some
helper macros to set a interrupt handler and disable/enable maskable
hardware interrupts.
Since there is no easy way to write an Interrupt Service Routines
(ISR) in C (for further information on this, see [1]), we introduce
the SET_INTERRUPT_HANDLER helper macro.
The macro does two things:
1) Defines an assembly trampolin to a C function that will, indeed,
handle the interrupt.
2) Sets the corresponding interrupt gate descriptor in IDT.
The macro usage is pretty straightforward. The macro is defined as
SET_INTERRUPT_HANDLER(num, has_error_code, handler) where:
@num: Interrupt number (0-255)
@has_error_code: 0 if processor doesn't push error code onto the
stack. Otherwise, set this argument to 1.
@handler: Pointer to function that should be called once the
interrupt is raised. In case has_error_code == 0
the function prototype should be the following:
void handler(void)
Otherwise, it should be:
void handler(struct interrupt_context context)
For instance, let's say we want to set a handler for a device interrupt
(for example, interrupt number 101). Remember, hardware interrupts don't
have error code. So we should have something like this:
void interrupt_handler(void)
{
/* Handling code here */
}
void my_device_init(void)
{
...
SET_INTERRUPT_HANDLER(101, 0, interrupt_handler);
...
}
Now, let's say we want to set an interrupt handler for Page Fault
(interrupt number 14). Some exceptions, such as Page Fault, pushes an
error code onto the stack and may require registers values in order
to be properly be handled. Thus, the code should look like this:
void pagefault_handler(struct interrupt_context context)
{
/* Handling code here */
}
void init_memory(void)
{
...
SET_INTERRUPT_HANDLER(14, 1, pagefault_handler);
...
}
For further information about exceptions and error code, refer to Intel
Combined Manual, Vol. 3, Sections 6.3 and 6.13.
Finally, we don't define any API to unregister interrupt handlers since
we believe that it wouldn't be useful at all, at least at this moment.
Considering Contiki's context, interrupt handler registration is pretty
"static" and defined at compile-time by platform code (or the device
drivers used by the platform).
[1] http://wiki.osdev.org/Interrupt_Service_Routines
94 lines
3.4 KiB
C
94 lines
3.4 KiB
C
/*
|
|
* Copyright (C) 2015, Intel Corporation. All rights reserved.
|
|
*
|
|
* Redistribution and use in source and binary forms, with or without
|
|
* modification, are permitted provided that the following conditions
|
|
* are met:
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
* notice, this list of conditions and the following disclaimer.
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
* documentation and/or other materials provided with the distribution.
|
|
*
|
|
* 3. Neither the name of the copyright holder nor the names of its
|
|
* contributors may be used to endorse or promote products derived
|
|
* from this software without specific prior written permission.
|
|
*
|
|
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
|
* ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
|
* LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
|
|
* FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
|
|
* COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
|
|
* INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
|
|
* (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
|
|
* SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
|
|
* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
|
|
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
|
|
* OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
*/
|
|
|
|
#include <stdint.h>
|
|
|
|
#include "helpers.h"
|
|
|
|
#define NUM_DESC 256
|
|
|
|
typedef struct idtr {
|
|
uint16_t limit;
|
|
uint32_t base;
|
|
} __attribute__((packed)) idtr_t;
|
|
|
|
typedef struct intr_gate_desc {
|
|
uint16_t offset_low;
|
|
uint16_t selector; /* Segment Selector for destination code segment */
|
|
uint16_t fixed:11;
|
|
uint16_t d:1; /* Size of gate: 1 = 32 bits; 0 = 16 bits */
|
|
uint16_t pad:1;
|
|
uint16_t dpl:2; /* Descriptor Privilege Level */
|
|
uint16_t p:1; /* Segment Present flag */
|
|
uint16_t offset_high;
|
|
|
|
} __attribute__((packed)) intr_gate_desc_t;
|
|
|
|
/* According to Intel Combined Manual, Vol. 3, Section 6.10, the base addresses
|
|
* of the IDT should be aligned on an 8-byte boundary to maximize performance
|
|
* of cache line fills.
|
|
*/
|
|
static intr_gate_desc_t idt[NUM_DESC] __attribute__ ((aligned(8)));
|
|
|
|
/* XXX: If you change this function prototype, make sure you fix the assembly
|
|
* code in SET_INTERRUPT_HANDLER macro in interrupt.h. Otherwise, you might
|
|
* face a very-hard-to-find bug in the interrupt handling system.
|
|
*/
|
|
void
|
|
idt_set_intr_gate_desc(int intr_num, uint32_t offset)
|
|
{
|
|
intr_gate_desc_t *desc = &idt[intr_num];
|
|
|
|
desc->offset_low = offset & 0xFFFF;
|
|
desc->selector = 0x08; /* Offset in GDT for code segment */
|
|
desc->fixed = BIT(9) | BIT(10);
|
|
desc->d = 1;
|
|
desc->dpl = 0;
|
|
desc->p = 1;
|
|
desc->offset_high = (offset >> 16) & 0xFFFF;
|
|
}
|
|
/*---------------------------------------------------------------------------*/
|
|
/* Initialize Interrupt Descriptor Table. The IDT is initialized with
|
|
* null descriptors. Therefore, any interrupt at this point will cause
|
|
* a triple fault.
|
|
*/
|
|
void
|
|
idt_init(void)
|
|
{
|
|
idtr_t idtr;
|
|
|
|
/* Initialize idtr structure */
|
|
idtr.limit = (sizeof(intr_gate_desc_t) * NUM_DESC) - 1;
|
|
idtr.base = (uint32_t)&idt;
|
|
|
|
/* Load IDTR register */
|
|
__asm__("lidt %0\n\t" :: "m" (idtr));
|
|
}
|