Accelerating Time-to-Market
Figure
4-1 . Infusion pump controller architecture .
When running directly on seL4 , DDS requires a custom library to provide key services that seL4 does not support ( libsel4osapi ). When using CAmkES , which provides these services , this library is no longer necessary .
1 . Running applications directly within the trusted user space of seL4 with no operating system
2 . Treating seL4 as a hypervisor and running applications within virtual machines ( VMs ).
A third architectural option is to combine these . We discuss each below . An important advantage of using DDS is that your application code will not be dependent upon seL4 – it can run in either architecture , along with numerous other OS / HW combinations . These applications can communicate with all other DDS applications running anywhere on your computer , network , or WAN . Moreover , these applications could all be running on different OS / HW and written in different languages .
The first option we present is to deploy your applications directly on seL4 / CAmkES along with a certifiable DDS library ( see Figure 4-2 ). As noted earlier , this option offers the most trustworthy solution . You can either utilize the CAmkES component framework or develop directly as a native seL4 library . In both cases , your applications would only need to invoke the interfaces provided
Journal of Innovation 97