2018 23rd Conference of Open Innovations Association (FRUCT) 2018
DOI: 10.23919/fruct.2018.8588018
|View full text |Cite
|
Sign up to set email alerts
|

VOSYSmonitor, a TrustZone-based Hypervisor for ISO 26262 Mixed-critical System

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
7
1

Relationship

0
8

Authors

Journals

citations
Cited by 10 publications
(5 citation statements)
references
References 0 publications
0
5
0
Order By: Relevance
“…Cereia and Cibrario carried out a similar exercise, implementing a virtualization layer that allowed to deploy an RTOS and a guest OS, pointing out some of the limitations that ARM TrustZone imposed on them at the time: it only allowed the execution of two OSs and, while the guest OS did not it could access or interfere with the RTOS, it did not work in reverse, so it would not support two secure RTOS [94]. These limitations are shared by ARM TrustZone-based hypervisors proposed in later work, such as the Secure Automotive Software Platform by Kim et al [95] or the open-source Xvisor presented by Cicero et al [96] VOSYSmonitor, from Virtual Open Systems, also allows parallel execution of a secure partition (running an RTOS) and a partition without real-time guarantees (GPOS), but has the particularity that it allows the non-critical partition (GPOS) to use another hypervisor (such as Xen or KVM), so it could be argued that it also supports multi-guest OS [97]. VOSYSmonitor gives full priority to the RTOS, allowing the GPOS(s) to run when there are no active tasks on the RTOS.…”
Section: E Other Hypervisorsmentioning
confidence: 99%
“…Cereia and Cibrario carried out a similar exercise, implementing a virtualization layer that allowed to deploy an RTOS and a guest OS, pointing out some of the limitations that ARM TrustZone imposed on them at the time: it only allowed the execution of two OSs and, while the guest OS did not it could access or interfere with the RTOS, it did not work in reverse, so it would not support two secure RTOS [94]. These limitations are shared by ARM TrustZone-based hypervisors proposed in later work, such as the Secure Automotive Software Platform by Kim et al [95] or the open-source Xvisor presented by Cicero et al [96] VOSYSmonitor, from Virtual Open Systems, also allows parallel execution of a secure partition (running an RTOS) and a partition without real-time guarantees (GPOS), but has the particularity that it allows the non-critical partition (GPOS) to use another hypervisor (such as Xen or KVM), so it could be argued that it also supports multi-guest OS [97]. VOSYSmonitor gives full priority to the RTOS, allowing the GPOS(s) to run when there are no active tasks on the RTOS.…”
Section: E Other Hypervisorsmentioning
confidence: 99%
“…Other than the OS and hypervisor modules, there are plenty of other modules which compose the MICROSAR Safe basic software which have all been certified by the ISO 26262 ASIL-D standard as SEooC [19]. VOSYSmonitor [20] is an ASIL-C ISO 26262-compliant hypervisor, developed for both ARMv7 and ARMv8 architectures whose Cortex-A processors offer the Secure Monitor mode. This feature allows executing a safety-critical RTOS and a general-purpose OS simultaneously; moreover, it allows the use of virtualization extensions like Linux/KVM, thus enabling the instantiation of multiple virtual machines.…”
Section: Related Workmentioning
confidence: 99%
“…VOSYSMonitor. VOSYSmonitor [115,116] is a lowlevel closed-source software layer that executes in the monitor mode of the ARM TrustZone architecture. It was conceived for the automotive industry and it is compliant with the ASIL-C requirements of the ISO 26262 standard [10].…”
Section: Arm Trustzone-assisted Virtualizationmentioning
confidence: 99%