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 [2018/09/21 14:15] waltminer [Meetings] Updated meeting time |
eg-virt [2019/06/26 14:51] m.paolino updates after discussion during eg-virt meeting |
||
---|---|---|---|
Line 14: | Line 14: | ||
- | Regular meetings are scheduled on Wednesdays at 4 PM CEST (bi-weekly). To join the discussion, please use the following link: | + | Regular meetings are scheduled on Wednesdays at 14:00 UTC (bi-weekly). To join the discussion, please use the following link: |
+ | |||
+ | Join Zoom Meeting | ||
+ | https://zoom.us/j/855006400 | ||
- | https://global.gotomeeting.com/join/728365005 | ||
Line 43: | Line 46: | ||
* Artem Mygaiev - EPAM - artem_mygaiev@epam.com | * Artem Mygaiev - EPAM - artem_mygaiev@epam.com | ||
* Jack Ren - Intel - jack.ren@intel.com | * Jack Ren - Intel - jack.ren@intel.com | ||
+ | * Khiem Nguyen - Renesas - khiem.nguyen.xt@renesas.com | ||
* Name - Company - email | * Name - Company - email | ||
* ... | * ... | ||
Line 48: | Line 52: | ||
The discussions of this EG will be done through the public AGL mailing list. | The discussions of this EG will be done through the public AGL mailing list. | ||
- | ====== ALS2017 virtualization related presentations ====== | + | ====== Hypervisor and eCockpit requirements ====== |
+ | |||
+ | Virtualization in the AGL Requirements: Eric Shufro, Satpreet Singh (Panasonic), LaurentC, Mark Silberger (VW) | ||
- | This section lists the EG-VIRT and virtualization related presentation to be held in Tokyo for ALS2017: | + | 1. Vision |
- | * [[https://als2017.sched.com/event/AF0V/how-to-introduce-virtualization-in-agl-objectives-plans-and-targets-for-agl-eg-virt-michele-paolino-virtual-open-systems|How to Introduce Virtualization in AGL? Objectives, Plans and Targets for AGL EG-VIRT]] - Michele Paolino, slides available here: [[http://events.linuxfoundation.org/sites/events/files/slides/vosys_EG-VIRT_ALS17_2017_6_1_public_0.pdf]] | + | * Have an opensource project supporting a e-cockpit out of the box solution. |
- | * [[https://als2017.sched.com/event/AF0M/an-opensource-low-level-hypervisor-for-agl-dominig-ar-foll-intel-open-source|An OpenSource Low Level Hypervisor for AGL]] - Dominig ar Foll | + | * Support IVI (android/AGL), cluster (AGL), Telematics (Connectivity), safe RTOS (AutoSAR, RTOS) |
- | ====== Known efforts for automotive virtualization ====== | + | 2. Hypervisor |
+ | * ability to virtualize GPU, IOs, networking, CPU and run different virtual machines. | ||
+ | * Support memory separation for each guest | ||
+ | * Support physical suspend to RAM. | ||
+ | * Inter VM communication (Shared memory, network, character) | ||
+ | * 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% | ||
- | 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. | + | 3. System Behavior |
+ | * Power management of vehicle micro and main micro | ||
+ | * Co-ordinate startup and shutdown of all VMs. | ||
+ | * 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. | ||
- | * 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 | + | 4. Goals |
- | * Description - company | + | * Create standard interfaces for inter VM communication. |
+ | * Create vehicle power moding strategy and interfaces to VM. | ||
+ | * Create a system block architecture with recommended separation of concerns. | ||
+ | * Standard way of sharing hardware (Virtio) is very important for fast prototyping and portability | ||
+ | * Standard way of software update including peripheral devices and delta update. | ||
+ | 5. HW target | ||
+ | * The new raspberry Pi can be a nice target |