20 | | 2. In each cluster the local '''HWI''' (hardware interrupts) generated by the local peripherals are ''statically'' allocated to local processors. |
21 | | 3. In each cluster, one '''PTI''' (timer interrupt) is statically allocated to each processor for context switch). The TICK period is defined by the GIET_TICK_VALUE parameter in the giet_config.h file. |
22 | | 4. In each cluster, 4 '''WTI''' (mailbox interrupts) called WAKE_UP, EXT_IRQ_ONE, EXT_IRQ_TWO, EXT_IRQ_TER are statically allocated to each processor. The first one is used by the GIET_VM boot-loader for processor wakup, and can be used by the kernel for inter-processor interrupts. The three other WTI mailbox are dynamically allocated to external IRQS generated by the external peripherals (through the IOPIC component), in order to route the external IRQ to the processor that launched the I/O operation. |
| 20 | 2. In each cluster the local '''HWI''' generated by the local peripherals are ''statically'' allocated to local processors. |
| 21 | 3. In each cluster, one '''PTI''' is statically allocated to each processor for context switch (pti_id = lpid). The TICK period is defined by the GIET_TICK_VALUE parameter in the giet_config.h file. |
| 22 | 4. In each cluster, 4 '''WTI''' mailbox (called WAKE_UP, EXT_IRQ_ONE, EXT_IRQ_TWO, EXT_IRQ_TER) are statically allocated to each processor. The first one is used by the GIET_VM boot-loader for processor wakup, and can be used by the kernel for inter-processor interrupts. The three other WTI mailbox are dynamically allocated to external IRQS generated by the external peripherals (through the IOPIC component), in order to route the external IRQ to the processor that launched the I/O operation. |