...
This page contains weekly reports of the Virtual Open Systems activity about the "AGL Native VIRTIO phase 2" project.
week 17
GPU:
Activity continues aiming at finalizing the port of the hw/virtio/vhost-user-gpu.c dependencies for the rendering framework and the vhost-user-gpu protocol. On virtio-loopback-adapter we added support for the VirtIOGpu device that implements the display framework backend of QEMU. Isolated and extracted the top-level GTK hooks and the display-listener used by QEMU. Next steps include finalizing the vhost-user-gpu support on the adapter and the port of display dependencies from QEMU.
As mentioned last week, there is a small delay on this task, however we plan to produce a first delivery before the next SDV call.
CAN:
This week we established communication between adapter / vhost-user-can backend and added most of CAN characteristics in the backend. During this communication, the two user-space components exchange virtio features, vhost-user features, queue number, queue size, etc. but they do not exchange any data. During the sub-task, we develop vhost-user-can backend in order to receive/send messages to adapter and integrate CAN related missing parts into the backend implementation, which were taken from QEMU's virtio-can device. Next week our effort will be focused on operating this whole structure with virtio-can driver and mainly on the data exchange process between the two components
week 16
GPU:
This week we identified the GPU rendering issues we were experiencing as dependent on the virtio-gpu driver to allow access on the framebuffer resource. There is then a need to remove kernel-space dependencies and fully render GPU graphics in user-space inside the adapter application. As a result, we are now working in that direction, updating the adapter's vhost-user-gpu support with the SDL rendering pipeline of Qemu. This could lead to a small delay in the delivery of the GPU support (initially planned for Oct. 31st). We will provide more info with a new deadline next week.
...