Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

DeviceStatusStart dateFirst Patch release (gerrit)Expected due date
GPUongoing2023-07-03week 40~End of Oct. 2023
sounddone2023-07-03week 41~End of Oct. 2023
GPIOdone2023-08-28week 40~End of Oct. 2023
CANongoing2023-10-09week 4408/12/2023
console-

end of 2023
AWS AMI creation

-



end of 2023

...

This page contains weekly reports of the Virtual Open Systems activity about the "AGL Native VIRTIO phase 2" project.


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.

CAN:     
Finish an initial draft version of vhost-user-can under the adapter. A new vhost-user-can device was implemented under adapter which compiles without error and it is ready to be tested with a backend device. In parallel, continue working with vhost-user-can under rust-vmm project. An initial draft version, was already in place but the device is not mature enough to be compiled and tested with adapter's component. Next week, we target to have an first communication between adapter and backend device, exchanging virtio and vhost-user features, queue number, sizes etc.

week 15

GPU:

Updated the virtio-loopback-adapter GPU's support and split the frames-rendering part to a standalone application. This is intended to result in a viewer-application that uses standardized DRM/KMS APIs to retrieve and render frames from the character device that is probed by the virtio-gpu driver. Performed tests to verify the virtio-gpu probed driver state and the message exchanges with vhost-user-gpu. Tested the virtqueues management and the events/irqs received by the virtio-loopback-adapter threads with success.
Next steps include completing and resolving the issues on the viewer-application for virtio-gpu.

...