...
Based among other things on the idea presented at GENIVI AMM in Munich regarding VIRTIO use both with and without hypervisor, to communicate between multiple OSes, the need has been identified to describe the complexity of system design on modern heterogeneous multi-core SoCs, running several different Operating System kernel instances.
| Anchor | ||||
|---|---|---|---|---|
|
Proposed Document Outline
Focus: "What HV technology can do for future automotive systems."
1 Motivation: Why to use HV:
- Use of legacy systems with minor modifications,
- address what kind of modifications we expect,
- address problem of open source firmware and driver (MCAL) qualification when running virtualized drivers (see also section 3). HV helps with this by
- isolating critical devices from non-critical ones, allows one to build systems with mixed-criticality w.r.t. safety-relevance.
- qualified driver needs to come with the driver host or even the HV provider
- Use of special purpose Guest/OS for isolating a specific functionality, i.e., building safety and security island
- Sharing of HW in the presence of parallel system executions
- Isolation properties in the presence of parallel systems executions:
- Spatial isolation, hiding of secrets
- Temporal isolation, implicit and explicit shared resources…
2 What does the HW need to fulfill to support unmodified execution of complete SW stacks.
This is directed towards the HV vendor to avoid the problems we have seen in the past.
3 Isolation and Partitioning
multiOS vs. HV
Timing and Spatial isolation
Different types of HV to support partitioning (see Gunnars list)
4 Inter-core communication
VM2VM
HV2VM
And HV-off partition to VMs
5 Sharing of physical devices
What does a HV need to do, to make its usage agnostic to Guest/OS:
Here we place the story on Virtio and generic interfaces
...
Title candidates
(depend on actual content)
Next Generation Multi-OS System Design
Multi-OS System Design on Multicore SoCs
What HV technology can do for future automotive systems.
...
Content Brainstorm
Intro. Why ? Motivation
-- consolidation of systems, "mixed criticality" requirements, e.g. security, safety, real-timedness.
This background is well know... Previous AGL white paper intro should cover this quite well, for example.
Generally try reuse, don't redo, and complement with what is missing.
...
- System Architects - system design guidance
- Guiding purchasing of ECU systems... requirements on the hardware and software stacks
- HW / SoC designers (for the needed HW features)
- IP-vendors (ARM, Synopsys, Imagination Technologies, Cadence)
Title candidates
(depend on actual content)
Next Generation Multi-OS System Design
Multi-OS System Design on Multicore SoCs
What HV technology can do for future automotive systems.
Proposed Document Outline
Focus: "What HV technology can do for future automotive systems."
1 Motivation: Why to use HV:
- Use of legacy systems with minor modifications,
- address what kind of modifications we expect,
- address problem of open source firmware and driver (MCAL) qualification when running virtualized drivers (see also section 3). HV helps with this by
...
...
EARLIER/OTHER outline proposal
and some other details ...
...
- Use of special purpose Guest/OS for isolating a specific functionality, i.e., building safety and security island
- Sharing of HW in the presence of parallel system executions
- Isolation properties in the presence of parallel systems executions:
- Spatial isolation, hiding of secrets
- Temporal isolation, implicit and explicit shared resources…
2 What does the HW need to fulfill to support unmodified execution of complete SW stacks.
This is directed towards the HV vendor to avoid the problems we have seen in the past.
3 Isolation and Partitioning
multiOS vs. HV
Timing and Spatial isolation
Different types of HV to support partitioning (see Gunnars list)
4 Inter-core communication
VM2VM
HV2VM
And HV-off partition to VMs
5 Sharing of physical devices
What does a HV need to do, to make its usage agnostic to Guest/OS:
Here we place the story on Virtio and generic interfaces
BACKUP/EXTRA
Not agreed to be in scope
and some other details
(from another outline proposal)?
1. Introduction
Intro: Need for multi-OS design. Possibilities given by modern hardware, hypervisors and other techniques
...