User Tools
bof-hypervisor
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
bof-hypervisor [2016/08/04 15:21] mpaolino Moving contributors at the end of the page |
bof-hypervisor [2017/02/01 17:36] (current) waltminer changed link to EG |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ====== Abstract ====== | ====== Abstract ====== | ||
| - | Possible new EG to be created. | + | 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 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. | + | 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 45: | Line 45: | ||
| ====== Proposed to do list for the Virtualization Expert Group ====== | ====== 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?) | - 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?) | ||
| Line 53: | Line 55: | ||
| - Extensions development and integration in AGL | - Extensions development and integration in AGL | ||
| + | |||
| + | - Expand and improve AGL specifications Section 7.3 (Hypervisor) | ||
| ====== Contributions ====== | ====== Contributions ====== | ||
| - | Proposed by Michele Paolino (Virtual Open Systems) | + | Proposed by Michele Paolino (Virtual Open Systems, m.paolino@virtualopensystems.com) |
| ===== Contributors ===== | ===== Contributors ===== | ||
| + | |||
| + | Please add here your name, company, email: | ||
| .. | .. | ||
bof-hypervisor.1470324116.txt.gz ยท Last modified: 2016/08/04 15:21 by mpaolino
Page Tools
