...

• 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

...

What HV technology can do for future automotive systems.

...

Proposed Document Outline

...

Focus: "What HV technology can do for future automotive systems."

...

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 Another direction: (Multi-OS design proposal)

1. Introduction

Intro: Need for multi-OS design.  Possibilities given by modern hardware, hypervisors and other techniquesDefine Target audience

2. Isolation and Partitioning

Intro.  Talk about Partitioning and Spatial/Timing isolation of parts.Partitioning Technologies

1. Full-scale Hypervisors
2. MCU Hypervisors
3. Dedicated Core partitioning
4. Operating System process partitioning / containers
5. Peripheral partitioning (or is this in later HW chapter)

3. Inter-core communication

...

4. Designing for Functional Safety

Describe specific features (hardware and software) supporting Functional Safety Goals

Design process

5. Designing for Cyber-security

Describe specific features (hardware and software) supporting Functional Safety Goals

TrustZone but also others

Design process

6. Hardware sharing

Hardware Device sharing - is the main purpose of Hypervisors.  
However device sharing can be set up with other means?
Yes, examples:

• h/w display layers
• GPU virtualisation with OS ID support

Specific Hardware Support

• GPU virtualization features
• GPU OS isolation
  • Separate input ports
  • GPU scheduler ensuring pipeline for each OS is serviced
  • Memory separation
  • Drawing isolation
    • Dedicated functional safety drawing paths, e.g. separate 2D rendering path for cluster telltales
• Other HW features
  • Bus Master / IP / Memory access isolation
    • Independent security and safety groups control access of IP on bus and memory protection
  • Multi-level security isolation outside of common IP such as TrustZone
    • e.g. Implementation in real time R7 CPU
  • Lifecycle Management
    • e.g. control of security at different stages of its life ← which chapter does this fit in?

• --> Some architectures can guarantee QoS on internal interconnects and caches, etc.  (what else?) controlled by VM configuration or h/w controls.

7. Selecting a Design

• Describe typical constraints and input that drives design decisions.
• Walk through the main characteristics of each method, and any other consequences of choosing one method or other.
• Guide the reader through the selection process, (comparing constraints to consequences of each choice)
  (Look at the "How to choose graphics sharing technology" presentation for inspiration)

8. Future outlook (?)

--> build something out of the "wish list"?

To be sorted

System-level quality of service.  What is this and where to fit in?

...