The comparatively short setup time reduces the time-to-market and makes this interesting for systems that need hard real-time, mixed criticality and the extensive extension possibilities of a mighty yet lightweight Linux system.
PikeOS allows the execution of guest operating systems in two modes:
2. Hardware Virtualization
While the first mode runs on each supported PikeOS architecture without requiring hardware virtualization support, it requires the guest operating system to be modified. The changes are mostly related to memory management at architecture level. The second mode does not require modification of the guest OS, but the configuration can be a bit more tricky. Due to the hardware virtualization the performance is better compared to the para virtualization when it comes to system call, exception and interrupt handling.
In terms of Linux, the kernel needs to be patched for para virtualization. In case of the hardware virtualization, usually the device tree provided to the boot loader needs to be tweaked a bit. Apart from that, any Linux distribution can be run on top of PikeOS. The only pre-condition is that the distribution supports the target architecture.
There are good reasons why you benefit from choosing ELinOS as the PikeOS Linux guest operating system:
Everything under one hood: CODEO IDE. The tools for PikeOS and ELinOS have the same look and feel and follow the same user-centric philosophy
Board Support Packages
ELinOS already provides BSPs for all variants of the PikeOS virtualization. The build system automatically chooses the right kernel for the correct architecture you have chosen
Advanced Drivers and Settings
Available for the PikeOS integration: These comprise the ARINC 653 queuing and sampling port API, PikeOS file providers, MTD (Memory Technology Device) drivers, shared memory and partition control