On 06.11.20 11:29, 'Nikhil Devshatwar' via Jailhouse wrote: > On 06:30-20201106, Liang Jingyan (M) wrote: >> >> 14. What the hypervisor have got Safety certification level? >> >> if no safety certification, pls share some introduce how does it make safety? >> >> > > I think the smaller code base, deterministic resource allocation and > other decisions are taken considering the usage of this hypervisor in > safety critical systems. This shoud ease in certification. > > However, there is no certification done for Jailhouse >
...and that is because of the lack of a suitable hardware platform - up to now - which provides the necessary safety properties in order to use the hypervisor as a safety element. Certifying the Jailhouse code base itself would be doable with reasonable effort (we actually discussed that with a certification authority, TÜV, already). However, that alone would not help you if you cannot map it on some real hardware. Check, e.g, if you can get a safety manual that covers the A-core MMU so that Jailhouse can rely on it (and/or check it during runtime) for establishing spatial partitioning. You can also watch [1] on that, namely the discussion at the end of my talk. It's old but - to my best knowledge - still valid in this regard, unfortunately. A good share of these issues we are currently trying to address via hardware/software co-design in a research project [2]. Jan [1] https://connect.linaro.org/resources/hkg18/hkg18-115/ [2] https://www.selene-project.eu/ -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux -- You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jailhouse-dev/484b82e2-8f05-485e-49e0-4e0ddbab989b%40siemens.com.
