0c9ce49d2a
When Zephyr runs directly on actual hardware, it will be always directing MSI messages to BSP (BootStrap Processor). This was fine until Zephyr could be ran on virtualizor that may NOT run it on BSP. So directing MSI messages on current processor. If Zephyr runs on actual hardware, it will be BSP since such setup is always made at boot time by the BSP. On other use case it will be whatever is relevant at that time. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com> |
||
|---|---|---|
| .. | ||
| core | ||
| include | ||
| zefi | ||
| CMakeLists.txt | ||
| gen_gdt.py | ||
| gen_idt.py | ||
| gen_mmu.py | ||
| ia32.cmake | ||
| intel64.cmake | ||
| Kconfig | ||
| timing.c | ||