Page History

...

• Recap from the previous week
  • See outline here: HV
  • Multi OS system design on heterogeneous multi-cores as a general topic
  • System wide QoS
  • Protocols
  • The need for hardware device sharing ()
  • Hardware wish list for virtualization friendly SoCs
    • BSP drivers in general 
    • firmware wishes
    • Hardware wishlists could become outdated at some point
  • We should avoid scope creep
  • Finding/Using the right terms
  • Target audiences...
• Hardware requirements
  • System design is unique and can be used in so many different ways
  • Hard to find a wish list of features
  • Make sure that mandatory and optional hardware features
  • How hard can the requirements be, what is the guiding function behind a certain hardware feature
  • Hardware requirement scope?
    • Trustzone/firmware interfaces
    • Architecture coverage (arm, x86...)
    • hardware virtualization support
  • There is a huge need to a virtualization hardware wish list, maybe is also makes sense to start a separate wish list already?
  • If hardware doesn't behave nicely, software needs to do more work
  • Expand the target audience to IP/HW vendors
  • Stephen: We might have two different topics here
  • Gunnar: The wish list is probably going to be spread out in the whole document
  • The whitepaper should convey the thinking behind the wish list 
  • AI: Create a wish list, not a a content provider
  • Bernhard can provide a description of heterogeneous system design
• Gunnar can check, where the doodle for the working session is

...

June 4, 2019

Minutes pendingby Kai Lampka

a)   White paper: discussion on potential sections. -everybody is aksed to llok again at https://www.automotivelinux.org/wp-content/uploads/sites/4/2018/06/GoogleDrive_The-AGL-software-defined-connected-car-architecture.pdf

For inspiration.

(i)                  Why are we doing this motivation also addressing heterogenous multicores:

(ii)                Use-case of SoC partitioning into safety- and security islands.

(iii)               Clarification of terminologies, para-virtulization, TCB, microkernel-based approaches, monolithic HV, type-1 and type-2 and embedded HV

1. what is needed in HW to achieve this. Detail on a “wish-list” for HW-vendors to support SoC virtualization
2. Differentiation to containers and drawback, a critical view on containers do’s and don’t, same holds for HV.

(iv)               What HW can do for isolation resp. platform partitioning

1. Spatial isolation
2. Timing Isolation: Contention on (implicitly shared infra-structure) and explicitly shared devices.
3. Coming to future HW-based solutions, e.g., MPAM

Please consult https://static.docs.arm.com/ddi0598/a/DDI0598_MPAM_supp_armv8a.pdf
for inspiration.

(v)                VirtIO as mean of

1. interaction of VM to VM, HV to VM and HV-off partitions to HV/VMs
2. Sharing of devices in the above setup.    Define also different capabilities of devices, vfunctions and “virtualization-ignorant” devices

b) Meeting on Virtio in Berlin AI: Kai sends doodle link  to Gunnar):

1. Planned to meeting CW 38 for addressing on
   1. VirIO spec contribution
   2. White paper as discussed above

c) Status of technical discussion (needs attendance of Artem), we defer this.

...

May 28, 2019

Participants

• Gunnar
• Phillipe
• Dmitry
• Vasco
• Matti

...