Real-Time, Safe and Certified OS
Roman Kapl <[email protected]> drivers, customer projects, development
Tomas Martinec <[email protected]> testing and certification
- 1
- © SYSGO AG · INTERNAL
Introduction
• PikeOS – real-time, safety certified OS • Desktop and Server vs.
• Embedded • Real-Time • Safety-Critical • Certified
• Differences
• Scheduling • Resource management • Features • Development
- 2
- © SYSGO AG · INTERNAL
Certification
• Testing • Analysis • Lot of time • Even more paper • Required for safety-critical systems
• Trains • Airplanes
- 3
- © SYSGO AG · INTERNAL
PikeOS
• Embedded, real-time, certified OS • ~150 people (not just engineers) • Rail • Avionics • Space • This presentation is not about PikeOS specifically
- 4
- © SYSGO AG · INTERNAL
PikeOS technical
• Microkernel
• Inspired by L4
• Memory protection (MMU)
• More complex than FreeRTOS
• Virtualization hypervisor • X86, ARM, SPARC, PowerPC • Eclipse IDE for development
- 5
- © SYSGO AG · INTERNAL
Personalities
• General
• POSIX • Linux
• Domain specific
• ARINC653 • PikeOS native
• Other
• Ada, RT JAVA, AUTOSAR, ITRON, RTEMS
- 6
- © SYSGO AG · INTERNAL
PikeOS Architecture
App. App.
App. App.
App. App.
Volume
System
Provider
Partition
PikeOS
(Native, POSIX, ARINC653, ...)
HW Virtualized
Guest OS
Linux, Android
Para-Virtualized
Guest OS
Linux, Android
File System
PikeOS Native
Device Driver
User Space /
Partitions
System
System
Extension
Extension
PikeOS SystemSoftware
PikeOS Microkernel
Kernel Space /
Hypervisor
Architecture
Support Package
Platform
Support Package
Kernel Level
Driver
- CPU1
- Serial
- CAN
- Ethernet
- Graphics
...
SoC /
Custom Hardware
Hardware
- 7
- © SYSGO AG · INTERNAL
Embedded
• Examples
• Tamagochi • Rail signal • ABS brake controller
• Usually does not have
• Lots of RAM • Beefy CPU • Keyboard and mouse • PC Case • Monitor
- 8
- © SYSGO AG · INTERNAL
Embedded peripherals
• Ethernet
• Sometimes with hardened connectors • May be real-time
• CAN • I2C • UART (Serial port) • JTAG for debugging
- 9
- © SYSGO AG · INTERNAL
Safety
• System does not harm the environment
• Safe aircraft does not harm or kill people during the flight
• ≠ flawless
• Safe backup
• Airbus A340 rudder can still be controlled mechanically
• Safe failure-mode
• “Closed” rail signal is safe
• Harmless
• In-flight entertainment
- 10
- © SYSGO AG · INTERNAL
Safety
• ≠ security
• but there are overlaps
• Safety needs to be certified • More important than features or performance
- 11
- © SYSGO AG · INTERNAL
Hard-realtime
• Must meet deadlines
• Missed deadline can affect safety
• Deadlines given by
• Physics
• Car must start breaking immediately
• Hardware
• Serial port buffer size – data loss
• System design
• HW and SW must cooperate
- 12
- © SYSGO AG · INTERNAL
Real-Time Scheduling
• Lot of theory about running the tasks in correct order
• NSWE001- Embedded and Real Time Systems
• In practice simple thread priorities
• QNX, FreeRTOS, PikeOS, VxWorks …
• Often without time quantum
• Unlike Linux
- 13
- © SYSGO AG · INTERNAL
WCET
• =Worst-Case Execution Time • How long will the code run?
• Willwe satisfy the deadline? • Upper bound (worst-case) is important
• Combination of code analysis and measurement • Jitter
• Context switches • Interrupt duration • Interrupt latencies
- 14
- © SYSGO AG · INTERNAL
Enemies of Real-Time
• Shared resources
• Heap, devices, scheduler, CPU time • Unpredictable state • Locking
• Multi-processor
• Locking less predictable • Shared
• Cache • Memory bandwidth • Other processor units?
- 15
- © SYSGO AG · INTERNAL
More enemies
• Modern hardware
• Lazy algorithms • Branch predictors • Out-of-order execution
• Unpredictable pipeline
• TLB, caches
• Modern OS features
• Paging, overcommit • Copy on Write • Thread migration
• Complexity in general
- 16
- © SYSGO AG · INTERNAL
Memory Management
• Sometimes no MMU at all
• FreeRTOS, some VxWorks
• Simple virtual to physical mapping
X Paging, memory mapped files, copy on write … Shared memory Memory protection (NX bit etc.)
• No (ab-)use of free memory for buffers
- 17
- © SYSGO AG · INTERNAL
PikeOS Kernel Memory
• User-space needs kernel memory
• Threads • Processes • Memory mappings
• Pre-allocated pools
• Safe limit • Avoids extra locks
- 18
- © SYSGO AG · INTERNAL
User-space memory allocation
• Heap allocator problems
• Locking • Allocator latency • Fragmentation • Unpredictable failures
• General rule: avoid malloc/free
• Except for initialization • Pre-allocate everything • Malloc/free is error prone anyway
• Or use task-specific allocator
- 19
- © SYSGO AG · INTERNAL
Scheduling
• ARINC653 (avionics standard) is common
• Time partitions + priorities
- 0ms 20ms 40ms
- 70ms 90ms
- 150ms
Active TP Scheme
- 1
- 2
- 1
- 3
- 4
Time Partition N
255
Time Partition 2
TP
Scheduler
Time Partition 1
Time Partition 0
...
Prio 255
254
254
...
...
...
0
0
TP0 is PikeOS extension
- 20
- © SYSGO AG · INTERNAL
Multi-Processor
• Threads are bound to single CPU
• Explicit migration • PikeOS has implicitmigration on IPC • Scheduler ready queues per-CPU
• Kernel should avoid locks • Especially in real-time syscalls • If locks are fair (FIFO queue), WCET is
• num_cpus * lock_held_time
- 21
- © SYSGO AG · INTERNAL
Multi-Processor
• Predicting resources like caches and memory is difficult • Disable HyperThreading
• it is not worth the trouble
• SYSGO’s recommendation “avoid the problem” • Better solutions are being investigated
CPU 2 CPU 1
Non-realtime APP1
Linux
- Idle
- Non-realtime APP3
- Non-realtime APP2
- Real-time APP
- 22
- © SYSGO AG · INTERNAL
Other considerations
• Worst-case complexity
• Hash-map is O(1) in practice, O(n) in worst case • AVL or RB trees are always O(log n)
• Log messages may slow you down • Keep the code small (certification)
• Sadly, it often is better to copy and specialize the code
• Build time design
• Static number of FDs, buffers etc.
- 23
- © SYSGO AG · INTERNAL
Other considerations
• Choose a suitable HW
• NXP, Xilinx …
• Control over the platform
• You are not alone on X86 • System Management Mode • Intel Management Engine
- 24
- © SYSGO AG · INTERNAL
Coding guidelines
• MISRA C coding standard
• Ex. Rule: Initializer lists shall not contain persistent side effects
• In OS development, you have to break some of them
• Ex. Rule: A conversion should not be performed between a pointer to object and an integer type
- 25
- © SYSGO AG · INTERNAL
Mixing critical and non-critical …
- 26
- © SYSGO AG · INTERNAL
Why microkernel?
• Separate critical and non-critical components
• MMU required
• We need to certify
• The critical components • The kernel • Smaller kernel = less work
• Non-critical parts can use
• Off-the-shelf software • Linux • => Easier development
- 27
- © SYSGO AG · INTERNAL
Why microkernel?
• Alternatives
• Certify everything • Build two physically separate systems
• In PikeOS you can choose
• Kernel driver • User-space driver
• Clear(er) line between levels of criticality
• Desktop PC crash is not fatal if you save your work
- 28
- © SYSGO AG · INTERNAL
Mixed criticality ex.
• Typical examples of mixed criticality:
• Control loop (critical) vs. diagnostics (non-critical) • Combined Control Unit for multiplefunctions in car
- Leastcritical
- Most critical
- 29
- © SYSGO AG · INTERNAL
Partitioning example - Airbus A400M
- Level B
- Level B
- Level C
- Level D
Ramp, Doors, Aerial Delivery,
Cargo Locks
...
Graphics OpenGL
GUI
Winches,
Crane
....
9 Applications incl.
Waste&Water
HMI
PikeOS Virtualization Platform
Hardware
Pictures: Rheimetall Defense A400M
- 30
- © SYSGO AG · INTERNAL