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/05/15 14:19] singhsat [Hypervisor requirements] |
eg-virt [2019/06/26 14:51] m.paolino updates after discussion during eg-virt meeting |
||
|---|---|---|---|
| Line 54: | Line 54: | ||
| ====== Hypervisor and eCockpit requirements ====== | ====== Hypervisor and eCockpit requirements ====== | ||
| - | Virtualization in the AGL Requirements: Eric Shufro, Satpreet Singh (Panasonic) | + | Virtualization in the AGL Requirements: Eric Shufro, Satpreet Singh (Panasonic), LaurentC, Mark Silberger (VW) |
| 1. Vision | 1. Vision | ||
| - | * Have an opensoruce project supporting a ecockpit out of the box solution. | + | * Have an opensource project supporting a e-cockpit out of the box solution. |
| - | * Support IVI (android/AGL), cluster (AGL), safe RTOS (AutoSAR, RTOS) | + | * Support IVI (android/AGL), cluster (AGL), Telematics (Connectivity), safe RTOS (AutoSAR, RTOS) |
| 2. Hypervisor | 2. Hypervisor | ||
| Line 66: | Line 66: | ||
| * Inter VM communication (Shared memory, network, character) | * Inter VM communication (Shared memory, network, character) | ||
| * Meet ASIL Safety requirements | * 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 | ||
| Line 71: | Line 73: | ||
| * Co-ordinate startup and shutdown of all VMs. | * Co-ordinate startup and shutdown of all VMs. | ||
| * Support early boot using suspend to ram or suspend to disk or other techniques | * Support early boot using suspend to ram or suspend to disk or other techniques | ||
| - | * Interprocessor communication for different systems (IVI, cluster) including safety considerations. | + | * Interprocessor communication (bootmicro and mainmicro for different systems (IVI, cluster) including safety considerations. |
| 4. Goals | 4. Goals | ||
| Line 77: | Line 79: | ||
| * Create vehicle power moding strategy and interfaces to VM. | * Create vehicle power moding strategy and interfaces to VM. | ||
| * Create a system block architecture with recommended separation of concerns. | * Create a system block architecture with recommended separation of concerns. | ||
| - | * Standard way of sharing hardware (Virtio) | + | * 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. | * Standard way of software update including peripheral devices and delta update. | ||
| + | 5. HW target | ||
| + | * The new raspberry Pi can be a nice target | ||
eg-virt.txt · Last modified: 2023/04/19 20:46 by megankn
Page Tools
