July 22, 2020
- Topic 1: Messages & Information from AMM Meeting (Jerry, Jiancong Zhao, Walt Miner)
- VirtIO is officially declared as a new feature in AGL KK in the roadmap sharing by Walt.
- VirtIO related discussion was carried out in the advisory board, and following agreement achieved.
- agl-dev-community@lists.automotivelinux.orgIntegration of VirtIO into AGL has been accepted by Advisory Board.
- Study VirtIO as a candidate of the standard reference HAL interface for eco-system enhancement (including non-hypervisor environment)
- Keynote Session about VirtIO and a proposal of unified virtualized display by Panasonic
- Breakout Session about VirtIO technical sharing by OpenSynergy
- Topic 2: Presentation & Demo from Panasonic (Tsubone-san)
- Unified Virtual Display
- Details can be found in the keynote: https://static.sched.com/hosted_files/aglammsummer2020/3e/Device%20Virtualization%20Architecture%20in%20Automotive_Mashaige%20Mizuyama.pdf
- Topic 3: Linaro VirtIO Roadmap follow-up discussion- Technical Q&A (Alex, Vincent)
- Presentation slide : https://drive.google.com/file/d/12qcg5TNQhPYpptK3B0DAMJz-VQ0S0hZp/view?usp=sharing
August 5, 2020
- Topic 1: Yocto Architecture for VirtIO FEDD integration Mikhail Golubev
- some SoC vendor's BSP kernel doesn't support Yocto Linux so that the virtio.scc may be not included.
- it's better to maintain the front end driver or the kernel configuration in AGL.
- Release candidate branch for AGL will be in January.
- general idea is on master, but for recipe (patch and yocto layer only) → sandbox, source code → code repository
Jerry, Jiancong Zhao need to check with Walt Miner on application of a new repository (JIRA ticket)
- Topic 2: VirtIO Backend Related Sharing Laurent Cremmer
- Presentation slide: AGL EG-Virt.pdf
- Topic 3: GSoC Project Progress Sharing Month #2 Parth Dode Jakub Luzny → move to next EG
August 19, 2020
- Topic 1: GSoC Project Progress Sharing Month #2 Parth Dode Jakub Luzny
- Topic 2: Follow-up Proposal for VirtIO Front-end Integration Mikhail Golubev
- Topic 3: Guest Speech on Xen Argo with VirtIO by Edgeform Chritopher Clark & Rich Persaud
Remaining Action Items:
- Jerry, Jiancong Zhao need to check with Walt Miner on application of a new repository (JIRA ticket)
- Walt Miner to find the editable doc for original AGL white paper.
September 2, 2020
- Topic 1: Final Presentation of GSOC Jailhouse Project Jakub Luzny Parth Dode
- Topic 2: Follow-up Q&A about virtio-argo (Chritopher Clark & Rich Persaud)
- Topic 3: Conclusion & Future Plan of AGL KK VirtIO Integration Mikhail Golubev
Mikhail Golubev please upload the slide you presented in last EG
September 16, 2020
- Topic 1: Future Plan of VirtIO Device in AGL
- virtio-can not virtio-vehicle (virtio-can also include LIN)
- virtio-camera: what is up with DRM?
- virtio-tuner not virtio-radio (Linux v4l2 interface)
- ACRN has smth for USB → needs to be checked
- GNSS via virito-scmi? → needs to be checked
- Mikhail Golubev to upload the slide.
September 30, 2020
- Topic 1: Future Plan of VirtIO Device in AGL
- How we can brainstorm what kind of virtio devices are necessary to AGL
- method 1: invite IVI, IC experts from other EG to join the discussion
- Email in the mailing list is okay
- Inter-EG activities are handled in the SAT
- Announce & Invite in Dev Call is also possible (most people)
- method 2: invite GENIVI AVPS member to share their progress on the automotive virtio discussion
- method 1: invite IVI, IC experts from other EG to join the discussion
- What is our policy to decide which device should be integrated into AGL
- Option 1 (most strict): Only if the device has been upstreamed and official published in the OASIS specification
- Publish of OASIS specification will be the trigger for AGL virtio porting activities
- Option 2 (moderate): If the device has been upstreamed and has a certain plan to be included in the OASIS specification in near future
- Option 3 (most loose): Any devices that Virtualization EG members have consensus
Discussion: - Upstreamed drivers are mandatory
- Depending on AGL kernel version, some new devices may not be included. Backporting from the newer kernel is needed (in some circumstances, trouble may happen) → discuss whether it can be integrated in the form inside kernel trees or out of the kernel trees
- New device drivers (not upstreamed) has the similar situation with the above
Conclusion:
Depending on the maturity of the virtio device drivers, we can put into different places → all virtio drivers can be integrated in this way - Recipe: Put the new drivers to the meta-agl-devel for developing and testing, integrate the stable drivers in the meta-agl.
- Source Code: Staging (new drivers) & Src (stable drivers)
- Option 1 (most strict): Only if the device has been upstreamed and official published in the OASIS specification
- How we can brainstorm what kind of virtio devices are necessary to AGL
- Topic 2: OpenSynergy Plans for ALS VirtIO PoC & AGL KK Contribution Mikhail Golubev