User Tools

Site Tools


bof-hypervisor

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
bof-hypervisor [2016/08/04 15:05]
mpaolino Added architecture proposal to foster the community discussion
bof-hypervisor [2017/02/01 17:36] (current)
waltminer changed link to EG
Line 1: Line 1:
 BoF to be held during the AGL AMM in Munich on September 7-8, 2016 BoF to be held during the AGL AMM in Munich on September 7-8, 2016
  
-Possible new EG to be created. ​+====== Abstract ​ ======
  
-Virtualization can be used to provide HW isolation (memory, interrupts, etc) and to achieve ECU consolidation and portability. However, it brings new challenges to the automotive and the AGL community, including scheduling, safety, certification,​ security, RT responsiveness and HW acceleration (e.g., GPU virtualization and secure isolation). The recent availability of automotive platforms/​SoCs with virtualization extensions (e.g., Renesas R-Car-H3, Tegra TX1, etc), makes the use of virtualization in automotive possible.This BoF will also consider the benefits and trade-offs of using Linux Containers instead of a hypervisor. ​+All the hypervisor discussion are ongoing in the [[eg-virt|AGL-VEG]] group. 
 + 
 +Virtualization can be used to provide HW isolation (memory, interrupts, etc) and to achieve ​Electronic Control Unit (ECU) functions ​consolidation and portability. However, it brings new challenges to the automotive and the AGL community, including scheduling, safety, certification,​ security, RT responsiveness and HW acceleration (e.g., GPU virtualization and secure isolation). The recent availability of automotive platforms/​SoCs with virtualization extensions (e.g., Renesas R-Car-H3, Tegra TX1, etc), makes the use of virtualization in automotive possible.This BoF will also consider the benefits and trade-offs of using Linux Containers instead of a hypervisor. ​
  
 This BoF session will be be used to gather requirements for HW isolation and determine if there is enough interest in the topic to form an ongoing Expert Group. This BoF session will be be used to gather requirements for HW isolation and determine if there is enough interest in the topic to form an ongoing Expert Group.
Line 9: Line 11:
 ====== AGL virtualization proposed architecture ​ ====== ====== AGL virtualization proposed architecture ​ ======
  
-===== Requirements =====+In the following proposal, Intel and ARMv8 architectures are considered to address the following requirements:​ 
 - Single RTOS and single non critical environment running concurrently - Single RTOS and single non critical environment running concurrently
 +
 - Single RTOS and multiple non critical environments running concurrently - Single RTOS and multiple non critical environments running concurrently
 +
 - Multiple RTOSes and multiple non critical environments running concurrently - Multiple RTOSes and multiple non critical environments running concurrently
  
Line 17: Line 22:
 {{ :​agl_architectureproposal.png |}} {{ :​agl_architectureproposal.png |}}
  
-====== Contributions ​ ======+AGL community members are invited to validate and extend these requirements with more information and with respective use cases. Additionally,​ these architecture pictures (which show one of the possible solutions) are intended as a proposal for discussion. Needless to say that the final AGL architecture has to be agreed by the AGL community.
  
-Proposed by Michele Paolino (Virtual Open Systems)+===== Use Cases =====
  
-===== Contributors ​=====+TBC 
 + 
 +===== AGL Virtualization requirements ​===== 
 + 
 +- Single RTOS and single non critical environment running concurrently 
 + 
 +- Single RTOS and multiple non critical environments running concurrently 
 + 
 +- Multiple RTOSes and multiple non critical environments running concurrently
  
 .. ..
Line 31: Line 44:
 2) Share use cases 2) Share use cases
  
 +====== Proposed to do list for the Virtualization Expert Group ======
  
 +This is a first list of the work to be done by an eventual AGL Virtualization Expert Group (VEG):
 +
 +- Requirements and use cases definition (when is virtualization needed? which are use cases of interest? what do we need to implement virtualization?​ Which kind of virtual Electronic Control Unit are of interest?)
 +
 +- Analysis of the SoA technologies (Type 1 vs Type 2, comparison with other technologies such as containers, TrustZone, etc.) and open source projects (KVM, QEMU, XEN, libvirt, etc)
 +
 +- Identify the potential extensions from open-source upstream projects according to the identified requirements
 +
 +- Extensions development and integration in AGL
 +
 +- Expand and improve AGL specifications Section 7.3 (Hypervisor)  ​
 +
 +
 +====== Contributions ​ ======
 +
 +Proposed by Michele Paolino (Virtual Open Systems, m.paolino@virtualopensystems.com)
 +
 +===== Contributors =====
 +
 +Please add here your name, company, email:
 +
 +..
bof-hypervisor.1470323120.txt.gz · Last modified: 2016/08/04 15:05 by mpaolino