Agenda:
→ Announce the new virtio feature and reference implementation on KK in AB and AMM(?) Walt Miner
→ After moving to meta-agl, it can be announced
A draft of two/three scentences are needed
Build Instruction → e.g. https://docs.automotivelinux.org/en/master/#0_Getting_Started/2_Building_AGL_Image/5_2_Raspberry_Pi_4/
Jan-Simon Moeller create new category for virt-EG to write documentation about virtio
Harunobu Kurokawa - Renesas
Masahiro Hasegawa - Renesas
Venkata Ramalinga Prasad Tadepalli
Agenda:
https://gitlab.freedesktop.org/olv/drm-misc-next/-/commit/6b2013a48528fc9ea1e82c6b68c85521f6d03041
Agenda:
Agenda: 2nd workshop to Discuss how to achieve zero-copy for VirtIO GPU (3d mode)
Workshop Topic:
Follow up discussion on how to achieve Zero-Copy for VirtIO-GPU (3d mode)
Workshop Agenda:
Agenda:
|
Intel pioneered VFIO; Huawei did develop so called "warpdrive" technology → mainly for "server" hardware acceleration encryption & decryption (kind of passthrough but can be shared across different VMs)
https://connect.linaro.org/resources/bkk19/bkk19-401/
Type 1 hypervisor can passtrhough device for guest VM easily. But driver need to be have in the front end guest. (will be dependent onto SoC platform)
IOMMU should be able used but not used in the crosvm (instead, used host allocation). Coherent memory is needed.
Hello, Jerry, Nice meeting you. We are happy to discuss UADK with colleagues of the same profession. We are just afraid that we cannot give what you need;). Because it seems you are looking for VFIO rather than UADK. We tried to merge our requirement to VFIO initially. But we gave up after the first RFC. To us, the major down side of VFIO is that it is a practical device. But we don’t take it a device. We take it a heterogeneous CPU. In UADK, the process attach to the accelerator, the accelerator share whole or part of the address space of the process. So the process can deliver task to the accelerator without warrying how to copy data to the accelerator. So there is no independent device is created, no DNA operation is provided. It is just for sharing memory between CPU and the accelerator. Because of this, we solve different set of problem. E.g. we have to take care of process-cloning to duplicate/stop the interface to child process. But it seem you are looking for a solution to isolate some GPU resource for particular VM. This is exactly what VFIO trying to do. So now it is you who may want to tell me. Are you guys really want to know the detail of UADK? J Cheers |
Agenda:
Agenda:
Agenda:
Devices without standard VirtIO (in order to make virt-AGL applicable for real-world production)
Standard Devices but need improvement or extension for virtual AGL use case
Agenda:
Agenda:
Agenda:
Representative from Virt-EG:
Presented Slides:
Agenda:
Agenda:
Agenda:
Presented slides:
Agenda:
Presented slides:
Agenda:
Agenda:
Abstract:
Device virtualization has been a hot topic in the automotive world along with the increasing needs for ECU consolidation. VirtIO, one of the most mature para-virtualization frameworks, has been officially accepted as a common standard for device virtualization in AGL.
In this session, we will introduce achievements of AGL virtualization expert group on extending VirtIO in AGL to better fit automotive needs and share our thoughts on future trends of Software Defined Vehicle empowered by VirtIO which abstracts SW from HW (ECU, desktop and even cloud). We will also be sharing some VirtIO related demos from the member companies.
Agenda:
Agenda:
Agenda:
Agenda:
Abstract:
Device virtualization has been a hot topic in the automotive world along with the increasing needs for ECU consolidation. VirtIO, one of the most mature para-virtualization frameworks, has been officially accepted as a common standard for device virtualization in AGL.
In this session, we will introduce achievements of AGL virtualization expert group on extending VirtIO in AGL to better fit automotive needs and share our thoughts on future trends of Software Defined Vehicle empowered by VirtIO which abstracts SW from HW (ECU, desktop and even cloud). We will also be sharing some VirtIO related demos from the member companies.
Agenda:
→ discuss in next A