The idea is to pick specific virtualization topics, separately from the AVPS specification writing, and to do deep-dive investigations.
We did something similar with Graphics Virtualization a while back, where we had a series of sessions that invited experts in the graphics frameworks as well as hardware vendors speaking about their specific silicon technologies. This gave everyone involved a big boost in understanding of the area.
Brainstorm list:
(Next step is voting/prioritizing on these.)
Talk to your colleagues/experts in each area (not virtualization experts necessarily, but subject experts). Make them part of prioritization activity, have them tell us if they would like to attend a specific deep-dive on a topic.
- Crypto / Security
- Trusted Execution Environments
- Ethernet AvB / Time Sensitive Networking
- Google's Trout platform (likely subdivided into areas of interest)
- Microcontroller virtualization
- Automotive networks, in particular CAN
- Accelerators
- Tensor-Processing Units
- DSPs (is that discussion done or is there more?)
- Camera
- Real-timeish stuff
- What are the special considerations we need to work out to support real-time demands?
- Go through operating system kernel special needs for each popular OS choice.
- e.g. RTOS support? (VIRTIO might not apply? Or does it?)
- Impacts from safety certification, ASIL?
- Clock synchronization, real-time clock abstraction (probably a topic for the AVPS)
- Timer paravirtualization
- CPU scheduling reporting HV<->VM, e.g. kernels do not get accurate information about system load
- IPC
- Communication between different guests. Does it affect the Virtual Platform or is it just run transparently on virtual socket?
- Are there standard choices? Are there many vendor-specific proposals, like IC-COM?
- PCI
- used for example for inter-chip communication and peripherals
- Automotive working group exists within PCI v6 work
- Future interconnects: CCIX, CXL, Gen Z and other alternatives, NVidia alternative, ...