User Tools
eg-virt
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
eg-virt [2019/04/23 14:38] m.paolino Main page update, hypervisor requirements added |
eg-virt [2020/05/29 19:31] waltminer Updated EG members |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| Today the EG-VIRT expert group is focused on defining the Virtualization platform architecture of AGL. The result of the work of the EG-VIRT group in this direction is this [[https://www.automotivelinux.org/wp-content/uploads/sites/4/2018/06/agl_software_defined_car_jun18.pdf|white paper]]. | Today the EG-VIRT expert group is focused on defining the Virtualization platform architecture of AGL. The result of the work of the EG-VIRT group in this direction is this [[https://www.automotivelinux.org/wp-content/uploads/sites/4/2018/06/agl_software_defined_car_jun18.pdf|white paper]]. | ||
| + | In 2020 the Expert Group began to focus on making VirtIO available for AGL and various open source hypervisors. | ||
| For more information about the technical objectives, members involved and target events see the specific section below. | For more information about the technical objectives, members involved and target events see the specific section below. | ||
| Line 14: | Line 15: | ||
| - | Regular meetings are scheduled on Wednesdays at 14:00 UTC (bi-weekly). To join the discussion, please use the following link: | + | Regular meetings are scheduled on Wednesdays at 12:00 UTC (bi-weekly). To join the discussion, please use the following link: |
| Join Zoom Meeting | Join Zoom Meeting | ||
| Line 34: | Line 35: | ||
| This group is open to people interested in the AGL virtualization architecture definition and implementation. If you are interested in joining the development efforts or the discussion, put your name here. | This group is open to people interested in the AGL virtualization architecture definition and implementation. If you are interested in joining the development efforts or the discussion, put your name here. | ||
| + | * **Jerry Zhao - Panasonic - Expert Group Lead** | ||
| * Michele Paolino - Virtual Open Systems - m.paolino@virtualopensystems.com | * Michele Paolino - Virtual Open Systems - m.paolino@virtualopensystems.com | ||
| - | * Joel Hoffmann - Renesas Electronics - Joel.Hoffmann@renesas.com | + | * Matt Spencer - ARM |
| - | * Hariharan A - Sasken Technologies - hariharan.a@sasken.com | + | * Laurent Cremmer -Carmeq |
| - | * Yuichi Kusakabe - Fujitsu TEN - yuichi.kusakabe@jp.fujitsu.com | + | * Mark Silberberger - Carmeq |
| - | * Denys Balatsko - Global Logic - denys.balatsko@globallogic.com | + | * Joel Catala - Tuxera |
| - | * Christoffer Dall - Linaro - christoffer.dall@linaro.org | + | * Eva Rio - Tuxera |
| - | * Daniel Bernal - Arm Inc. - daniel.bernal@arm.com | + | * Francois Ozog - Linaro |
| - | * Tiejun Chen - VMware - tiejunc@vmware.com | + | * Victor Duan - Linaro |
| - | * Hampapur Ajay - Volterra - hajay@ves.io | + | * Mikhail Golubev- Open Synergy |
| - | * Ciwan Gouma - SYSGO - ciwan.gouma@sysgo.com | + | * Mikhail Zaytsev - MERA |
| - | * Artem Mygaiev - EPAM - artem_mygaiev@epam.com | + | * Leonid Lazerev - MERA |
| - | * Jack Ren - Intel - jack.ren@intel.com | + | * Kenji Hosokawa - ADIT |
| - | * Khiem Nguyen - Renesas - khiem.nguyen.xt@renesas.com | + | |
| - | * Name - Company - email | + | |
| - | * ... | + | |
| - | The discussions of this EG will be done through the public AGL mailing list. | ||
| - | ====== Hypervisor requirements ====== | + | The discussions of this EG are done through the public AGL mailing list. |
| - | Virtualization in the AGL Requirements: Eric Shufro, Satpreet Singh (Panasonic) | + | ====== Hypervisor and eCockpit requirements ====== |
| + | |||
| + | Virtualization in the AGL Requirements: Eric Shufro, Satpreet Singh (Panasonic), LaurentC, Mark Silberger (VW) | ||
| 1. Vision | 1. Vision | ||
| - | + | * Have an opensource project supporting a e-cockpit out of the box solution. | |
| - | a. Have an opensoruce project supporting a ecockpit out of the box solution. | + | * Support IVI (android/AGL), cluster (AGL), Telematics (Connectivity), safe RTOS (AutoSAR, RTOS) |
| - | b. Support IVI (android/AGL), cluster (AGL), safe RTOS (AutoSAR, RTOS) | + | |
| 2. Hypervisor | 2. Hypervisor | ||
| - | + | * ability to virtualize GPU, IOs, networking, CPU and run different virtual machines. | |
| - | a. ability to virtualize GPU, IOs, networking, CPU and run different virtual machines. | + | * Support memory separation for each guest |
| - | b. Support memory separation for each guest | + | * Support physical suspend to RAM. |
| - | c. Support physical suspend to RAM. | + | * Inter VM communication (Shared memory, network, character) |
| - | d. Inter VM communication (Shared memory, network, character) | + | * Meet ASIL Safety requirements |
| - | e. Meet ASIL Safety requirements | + | * OPTEE should be available for all the guests |
| + | * Boot time overhead introduced by the hypervisor should be much less than 25% | ||
| 3. System Behavior | 3. System Behavior | ||
| - | + | * Power management of vehicle micro and main micro | |
| - | a. Power management of vehicle micro and main micro | + | * Co-ordinate startup and shutdown of all VMs. |
| - | b. Co-ordinate startup and shutdown of all VMs. | + | * Support early boot using suspend to ram or suspend to disk or other techniques |
| - | c. Support early boot using suspend to ram or suspend to disk or other techniques | + | * Interprocessor communication (bootmicro and mainmicro for different systems (IVI, cluster) including safety considerations. |
| 4. Goals | 4. Goals | ||
| - | + | * Create standard interfaces for inter VM communication. | |
| - | a. Create standard interfaces for inter VM communication. | + | * Create vehicle power moding strategy and interfaces to VM. |
| - | b. Create vehicle power moding strategy and interfaces to VM. | + | * Create a system block architecture with recommended separation of concerns. |
| - | c. Create a system block architecture with recommended separation of concerns. | + | * Standard way of sharing hardware (Virtio) is very important for fast prototyping and portability |
| - | d. Standard way of sharing hardware (Virtio) | + | * Standard way of software update including peripheral devices and delta update. |
| - | e. Standard way of software update including peripheral devices and delta update. | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | ====== Known efforts for automotive virtualization ====== | + | |
| - | + | ||
| - | Currently available hardware platforms enable the implementation of different types of virtualization. This section gathers a list of example efforts in the direction of AGL virtualization. If you are working on a similar project and you want the AGL community to be aware of it, add the related information here below. | + | |
| - | + | ||
| - | * ALS 2016 PoC: AGL, FreeRTOS and Ubuntu running on the RCar H3 ([[http://www.virtualopensystems.com/en/solutions/demos/vosysmonitor-als2016|link]]) - Virtual Open Systems | + | |
| - | * Description - company | + | |
| + | 5. HW target | ||
| + | * The new raspberry Pi can be a nice target | ||
eg-virt.txt · Last modified: 2024/05/16 15:42 by wminer
Page Tools
