User Tools

Site Tools


eg-virt-meetings

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
Next revision Both sides next revision
eg-virt-meetings [2019/04/16 22:26]
singhsat
eg-virt-meetings [2019/05/15 13:27]
m.paolino [Meetings Agenda and Report]
Line 16: Line 16:
 ===== Meetings Agenda and Report ===== ===== Meetings Agenda and Report =====
  
-==== 16/04/2019, 4PM CET Meeting ​on 03/04/2019 Action item ==== +==== 15/05/2019, 4PM CET Meeting ==== 
-Virtualization in the AGL Requirements: Eric Shufro, Satpreet Singh (Panasonic) +AttendeesMichele Paolino (Virtual Open Systems), Walt Miner (Linux Foundation), ​Eric Shufro (Panasonic), Artem Myagev (EPAM), walzert 
-1. Vision + 
-   a. Have an opensoruce project supporting a ecockpit out of the box solution. +  * General updates 
-   b. Support IVI (android/AGL), cluster ​(AGL), safe RTOS (AutoSARRTOS) +  * Automotive virtualization requirements inputs from Panasonic:​ 
-2. Hypervisor  +    *  
-   ​a. ability to virtualize GPUIOs, networking, CPU and run different virtual machines. +  * Next call to be held in 12/06: 
-   b. Support memory separation for each guest +    * we'll skip May the 29th 
-   c. Support physical suspend to RAM. +  * Action points 
-   d. Inter VM communication ​(Shared memorynetwork, character) +    *  
-   ​e. Meet ASIL Safety requirements + 
-3. System Behavior +==== 17/04/2019, 4PM CET Meeting ==== 
-   ​a. Power ​management ​of vehicle micro and main micro +Attendees: Michele Paolino (Virtual Open Systems), Walt Miner (Linux Foundation), Eric Shufro ​(Panasonic)Artem Myagev (EPAM), walzert 
-   b. Co-ordinate startup and shutdown of all VMs. + 
-   ​c. Support early boot using suspend ​to ram or suspend to disk or other techniques +  * Automotive virtualization requirements inputs from Panasonic: 
-4. Goals +    * Key topic are Inter VM communication, ​power management and software updates 
-   ​a. Create standard interfaces ​for inter VM communication. +    * Suspend ​to ram and GPU virt are somehow already supported by XEN 
-   b. Create vehicle ​power moding ​strategy and interfaces to VM+    * System power management is missing in AGL (power on, screen off etc.) 
-   c. Create ​system block architecture ​with recommended separation of concerns. +        * In virtualized environments,​ there is need to power each virtual machine independently (power manager MCU that talks to plugins - one for each VM) 
-   d. Standard way of sharing hardware ​(Virtio+        * Today Tier-1s buy software from Vector to handle ​power moding ​states, communication framework, etc
-   e. Standard way of software update including peripheral devices and delta update.+        * Panasonic is available to join Linux Foundation and discuss with Vector to find solution for embedding solutions to this problem in AGL(also ​with closed binaries) 
 +        * On this topic, OEMs (Mazda/​Suzuki) are asking tier-1s to bring more production ideas to AGLPower management is one of them 
 +        * Today power management is done in EL3 (Arm TrustZone
 +    * A micro controller in the demonstration board is a nice feature to havePossibly with wake on CAN 
 +  * EG-IC 
 +    * Michele attended the last meeting, things are progressing but virtualization is not yet in their future plans 
 +  * Next call to be held in May 15th: 
 +    * we'll skip May the 1st 
 +  * Action points 
 +    * Artem to provide a couple ​of examples about IPC mechanismsIf this is not sufficient (Eric to check), we need to start describing a complex use case 
 +    * Michele will monitor EG-IC 
  
 ==== 03/04/2019, 4PM CET Meeting ==== ==== 03/04/2019, 4PM CET Meeting ====
eg-virt-meetings.txt · Last modified: 2023/04/12 11:38 by sbonazzo