Changes between Version 13 and Version 14 of kernel_interrupts

Timestamp:

Mar 14, 2015, 12:06:04 PM (9 years ago)

Author:

alain

Comment:

--

kernel_interrupts

@@ -2 +2 @@
 
 
-The [source:soft/giet_vm/giet_kernel/irq_handler.c irq_handler.c] and [source:soft/giet_vm/giet_kernel/irq_handler.h irq_handler.h] files define the kernel data structure and functions that are used to handle interrupts. They are prefixed by "_" to remind that they can only be executed by a processor in kernel mode.
+The [source:soft/giet_vm/giet_kernel/irq_handler.c irq_handler.c] and [source:soft/giet_vm/giet_kernel/irq_handler.h irq_handler.h] files define the kernel functions that are used to handle interrupts. They are prefixed by "_" to remind that they can only be executed by a processor in kernel mode.
 
 [[PageOutline]]
 
-The GIET_VM interrupt handler supports only the SOCLIB XCU interrupt controler. In a multi-cluster architectures, it must exist one XCU controller in all clusters containing processors. 
+The GIET_VM interrupt handler supports only the SOCLIB XCU interrupt controler. In a multi-cluster architectures, it must exist one XCU controller in ech cluster containing processors. 
 
-Each multi-channel XCU component in a given cluster must contain (NB_PROCS_MAX * IRQ_PER_PROCESSOR) channels  (one channel = one XCU output IRQ).
+A multi-channel XCU component in a given cluster must contain (NB_PROCS_MAX * IRQ_PER_PROCESSOR) channels  (one channel = one XCU output IRQ).
 
-There is three interrupt vectors per processor (stored in each processor's scheduler) for the three  interrupts types: HWI (Hardware Interrupt), PTI (Programmable Timer Interrupt), and WTI (Write Triggered Interrupt). Each interrupt vector entry contains two fields:
+There is three interrupt vectors per processor (stored in each processor's scheduler) for the three  interrupts types: '''HWI''' (Hardware Interrupt), '''PTI''' (Programmable Timer Interrupt), and '''WTI''' (Write Triggered Interrupt). Each interrupt vector entry contains two fields:
 ||isr_id         ||bits[15:0]    || defines the type of ISR to be executed ||
 ||channel_id ||bits[31:16]  || defines the channel for multi-channels ISR ||