Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Set current agenda and clean up backlog.

Purpose and Rationale

The Hypervisor Project follows after two successful workshops at the last is producing a common open licensed Automotive Standard Virtual Platform specification based on VIRTIO, and other standards.

On the more general scope, the project two GENIVI All-Member-Meetings and investigates the wide scope of open- source and commercial hypervisor technologies, and addresses challenges in their use.

   Through collaboration between all vendors, experts and adopters of virtualization technology we can lower the barriers to successful product development.

  The project primarily drives requirements, standardization for Hypervisor APIs, and other types of investigations to facilitate ECU consolidation, price reduction, and management of mixed-criticality in systems for improved security and functional safety.

You can look below for detailed backlog and topics, but to summarize there There are three primary work streams currently in development:

  1. Virtual Device API standardization, leading to the definition of the Automotive standard Virtual Platform
    (this naturally builds on existing standards like VIRTIO)collecting and driving requirements for a standard platform based on VIRTIO, SCMI, and other existing standards.

  2. Multi-OS system design on Multi-Core SoCs (with/without virtualisation)
  3. Investigate and recommend electrical/software architecture for automotive use-cases, when deployed using virtual-machine technologies. 

Next Meeting

...

Every Monday, 10:00 AM

...

CET

Agenda:

General backlog

  • AVPS v2 completed --> AVPS JIRA tickets for tracking 
  • Whitepaper planning (dormant at the moment)
  • Deep-dive Memory Buffer sharing (GPU) - suggested by Eugen Friedrich
  • Update Milestones, deliverables, and workplan.
  • Use-cases, architectures and requirements workstream (dormant)
  • Re-review scope of workand synergy opportunities,  AGL virtualization EG.  Links to previous papers below.
  • Establish scope of work and synergy opportunities for virtualization in AUTOSAR
  • Android and Trout, evaluation and establish relationship to AVPS.
  • Whitepaper progress (review page)
  • review and assignment of backlog and sprint tickets
  • F2F agenda finalization, agenda is here

Zoom Meeting details:

Upcoming F2F Meeting

Meeting Minutes (← use link)

Most Active Workstream:

  • Definition of Automotive Virtual Platform (a.k.a. API standardization for Hypervisors in automotive environment, with starting point in VIRTIO)

Backlog (Topic List)

(red star) Review / check consensus on USB chapter of specification + other minor edits (Artem to come back with new info)

  • AI/Tensor processing, on GPU or other dedicated hardware
  • Deep-dive Memory Buffer sharing (GPU) - invite Eugen Friedrich
  • Update Milestones, deliverables, and workplan.
  • (started, needs input again) Use-cases, architectures and requirements workstream
  • Some was added to the AGL publication on virtualization after our most recent review.  Re-review, to identify useful/reusable parts.  Links at the bottom.

Original sub-topics (Possible focus areas)

Meeting Minutes (← use link)

Resources

  Videos/recordings

  Related publications and input

Mailing list & Contribution

  1. Discussion should use the general genivi-projects mailing list(warning) Start the subject line using: [HVWS]
  2. The Wiki is an open public collaboration area.  Please contribute/improve it as needed.  Improve text, add relate info, links, references! 
    To edit the Wiki, log in or request an account.
  3. Any other process question? - you can contact the acting project lead:  Gunnar Andersson

Upcoming Events / F2F

GENIVI 20th All Member Meeting a Digital Experience


F2F Meetings (completed)

Original topic-list (possible focus areas)

  • APIs for security: Mandatory Access Control features (in virtualization environments, that is)
  • VM management tool
  • Instrumentation & tools
  • Safety compliance: ISO26262
  • Security compliance: Common Criteria, EAL
  • System design to optimize Boot Time,
  • Boot requirements, e.g. secure boot, integrity check,
  • Agree on Terms / Nomenclature

Done / skipped / no longer on backlog

...

The work is documented here

Other resources and Links

  Related publications and input

  Videos/recordings

  • Platform Security Summit May 23-24, 2018 - had several hypervisor related presentations – Youtube, (website)

Bangalore Technical Summit Agenda (2018 October) (← use link)

...

  ((green star) ^^ includes links to many topic presentations by the participants)

...