AMD Working On A New Backend For Improving ROCm Compute In QEMU/VMs
([AMD] 56 Minutes Ago
Better ROCm For GPU Virtualized Compute)
- Reference: 0001652413
- News link: https://www.phoronix.com/news/AMD-ROCm-Better-QEMU-VM
- Source link:
AMD engineers are working on enhancing the open-source ROCm compute stack for better handling GPU virtualized compute under QEMU.
Last year was a [1]merge request adding ROCm native context support for Virglrenderer. That ROCm native context support has yet to be merged into Virglrenderer for the AMD GPU compute stack for virtualized GPU computing. But now they are looking at a new implementation for providing better support in virtualized environments.
AMD engineer Honglei Huang started a new discussion today around developing a new back-end for ROCm GPU compute under QEMU. With the existing implementation using the VirtIO GPU context type and sharing the display path, they have encountered some roadblocks. Besides many accelerators lacking a display engine, leveraging the VirtIO GPU context type shared with the display path is causing contention and display stuttering. Compute contexts also typically need more memory access than what's allowed, and the ROCm stack not fitting nicely with the render model.
AMD thus is looking at implementing a dedicated headless VirtIO GPU instance solely for compute. They are also developing an open-source ROCm back-end library loaded in-process by QEMU that would be distributed in the future as part of their ROCm stack.
If this topic of AMD ROCm under QEMU for improved virtualized compute is of interest to you, [2]this mailing list thread is where the discussion has begun over this new possible back-end.
[1] https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/1568
[2] https://lore.kernel.org/dri-devel/4673d669-b350-4723-b74e-6e1ea5f09c22@amd.com/T/
Last year was a [1]merge request adding ROCm native context support for Virglrenderer. That ROCm native context support has yet to be merged into Virglrenderer for the AMD GPU compute stack for virtualized GPU computing. But now they are looking at a new implementation for providing better support in virtualized environments.
AMD engineer Honglei Huang started a new discussion today around developing a new back-end for ROCm GPU compute under QEMU. With the existing implementation using the VirtIO GPU context type and sharing the display path, they have encountered some roadblocks. Besides many accelerators lacking a display engine, leveraging the VirtIO GPU context type shared with the display path is causing contention and display stuttering. Compute contexts also typically need more memory access than what's allowed, and the ROCm stack not fitting nicely with the render model.
AMD thus is looking at implementing a dedicated headless VirtIO GPU instance solely for compute. They are also developing an open-source ROCm back-end library loaded in-process by QEMU that would be distributed in the future as part of their ROCm stack.
If this topic of AMD ROCm under QEMU for improved virtualized compute is of interest to you, [2]this mailing list thread is where the discussion has begun over this new possible back-end.
[1] https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/1568
[2] https://lore.kernel.org/dri-devel/4673d669-b350-4723-b74e-6e1ea5f09c22@amd.com/T/