Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Minute takers according to this page 

January 29February 5, 20182019

Participants:


  • Gunnar Andersson
  • Artem Mygaiev
  • Bernhard Rill
  • Christian Schulenberg
  • Dmitry Morozov
  • Franz Walkembach
  • Kai Lampka
  • Matt Spencer
  • Philippe Robin


Minutes


  • Last week's meeting review. Franz: RISC-V consortium and GENIVI board cooperation should be discussed. Gunnar sees no issue in trying new hardware architecture in the technical project, and GENIVI organization is generally hardware-independent.  Gunnar requests appropriate contact (from Franz), especially if someone works on Virtualization technologies.
  • Participation. No updates from Green Hills regarding a new participant → We have not reached out to our contacts, Philippe will do it.   Anup has a conflict on this time slot but wants to participate via email.  Gunnar proposes to shift the meeting (some of the time, not all of the time), for Anup, but also (maybe a different shift) to allow people from the US to participate.
  • SEL2.
    • Bernard: API specification (alpha revision) is about to be released. It will be accessible only under NDA. Artem proposes to create an internal review team.
    • Bernard could invite colleagues  to discuss SBSA (possibility to join in two weeks or so).
  • Draft specification. Gunnar: Last week I felt we did not have full agreement on what we want to achieve. The project description I will show later is one input to that discussion.
  • Come up with ideas for tech presentations for AMM meeting in Munich (May 14-16). Two weeks deadline has been proposed.
  • PV IO interface by Xen as an alternative to VirtIO. Artem proposes the topic for discussion. No documents with description so far. Artem is to share related links.
  • Reviewing Virtual Device Categories table. No progress. We need to clarify VM responsibilities. 

  • Also we need to convince people from OEMs to participate. We need requirements in general regarding usage of hypervisors in automotive.

    • Gunnar agrees, but proposes that we also know fairly well (as suppliers) the generalized use-cases and needs on a high level.  It is unfortunate but should not make us stop completely.
  • From interest to participation. Gunnar introduces the Project description: a high level idea of requirements and respective solutions. OCI as an example. Everyone is welcome to read and give some feedback. Franz asks about the list of VMs (OSes) we want to support. Gunnar: Any OSes that are in the scope of automotive industry (for example Linux (multiple variations), Android, QNX, INTEGRITY, AUTOSAR Adaptive).

Participants:

  • Franz Walkembach (taking minutes)
  • Philippe Robin
  • Gunnar Andersson
  • Dimitri Morozov
  • Vasco Fachin
  • Andreas Prosell
  • Artem Mygaiev
  • Erik Jaegervall
  • Vivek Galatage
  • Matt Spencer
  • Stephen Lawrence

apologies

  • Kai

Agenda:

  • Review previous week's minutes
  • Virtualization talks at the FOSDEM conference
  • API standardization / virtual platform definition
  • Backlog refinement and planning

Minutes:

  • Introduction of workgroup members and available content to the new team members
  • Review of last meeting minutes
  • Looking for RISC-V knowledgeable persons at Genivi
  • It was stated that RISC-V might be a good member for Genivi, but currently not important for the HV workgroup
  • AMM in Munich in May is approaching quickly
  • Gunnar gave feedback on the FOSDEM conference (link in Wiki) on 2 and 3 February in Brussels with some presentations on virtualization topics and tools, secure boot, virtual IOMMU implementation using HW nested paging. Virt audio by Red Hat
  • Artem: one update I wanted to share - finally Linaro OP-TEE (FOSS implementation of secure OS and environment for ARM Trust Zone) have just merged support for virtualization of guests running Trusted Applications that we've developed @EPAM & Xen Project: https://github.com/OP-TEE/optee_os/pull/2370, this allows native execution of TAs and can be included in spec
  • Draft of virtual platform definition, API and synergy document created by Gunnar, incl. auto requirements and scoping. Gunnar will post it on the Wiki for people that are interested
  • Erik is working on a group at Bosch focussing on security and was wondering how security influences the HV work group. We should work on a top level feature overview.
  • Andreas at Luxoft with PELUX open source platform that might include hypervisor technology including shared graphic functionality.
  • Vivek will investigate the work group content and get back with topics
  • Gunnar highlighted the contribution need to make the group successful
  • Philippe reminded all to propose topics for the AMM in May


January 29, 2019


January 22, 2019January 22, 2018

Participants:

  • Gunnar Andersson
  • Artem Mygaiev
  • Kai Lampka
  • Philippe Robin
  • Dmitry Morozov
  • Franz Walkembach
  • Bernhard Rill

...

  1. Franz suggested GENIVI community looking at RISC V architecture – this might become a production grade at some point
  2. Gunnar goes over last call’s minutes
  3. GHS: Nikola cannot join anymore because he changed position, GHS said they are interested in continuing their participation to the work
  4. Bernhard don’t have updates on SEL2 / SP805 yet
    1. Mentioned that discussion can happen with ARM engineers on WDT – but this is part of “supervisor” not hypervisor. This can be reviewed in scope of SBSA
    2. SEL2 – maybe some spec updates? Not yet
  5. Gunnar pointed out the need to take time schedules more aggressively
    1. Philippe suggested to use May 14-16 AMM in Munich as a milestone for some 1st version release and holding technical workshop on virtualization & spec review
    2. Gunnar requests for topics/proposals for presentations on GENIVI AMM (Artem wants to suggest reviewing pvif as alternative to virtio)
  6. Reviewing Virtual Device Categories table yet
    1. Block storage – no updates yet from Kai, Gunnar is reviewing goals and approach. One of the main un-covered topics is “automotive-grade persistency management” – does this imply some requirements on hypervisor level? Artem – hypervisor just shall not interfere. Gunnar – there may be 2 approaches: write-through with “privileged” processes or going through all system layers as usual. Kai – write down the requirements. Discussion continues into discussing API stability for all scenarios. Gunnar – does virtio provide everything needed for technical implementation of abovementioned? Kai – no, probably not, it does not allow applying policy, etc. Need to define what is missing, requirements, etc. From example of 2D GPU, Kai is asking – from this table it is not clear if virtio fits requirements. Gunnar – requirements must be checked against virtio spec. Kai – requirements as of now implying some design choices which may not be correct. Gunnar – yes, but requirements are there to support different implied designs, not to enforce them. Goal is to make a generic specification which can be tailored for a target system.

January 15,

...

2019

Participants:

  • Dmitry Morozov (OpenSynergy)
  • Artem (EPAM)
  • Gunnar (GENIVI)
  • Bernhard Rill (ARM)

...