On 20/3/24 21:50, dongwon....@intel.com wrote:
From: Dongwon Kim <dongwon....@intel.com>
QemuDmaBuf struct is defined and primarily used by ui/console/gl so it is
better to handle its creation, initialization and access within ui/console
rather than within hw modules such as hw/display/virtio-gpu and
hw/vfio/display.
To achieve this, new methods for allocating, initializing the struct, and
accessing certain fields necessary for hardware modules have been introduced
in ui/console.c.
(3rd patch)
Furthermore, modifications have been made to hw/display/virtio-gpu and
hw/vfio/display to utilize these new methods instead of setting up the struct
independently.
(1st and 2nd patches)
What about dbus_scanout_texture(), should it use dpy_gl_create_dmabuf()?
Dongwon Kim (3):
hw/virtio: intialize QemuDmaBuf using the function from ui/console
hw/vfio: intialize QemuDmaBuf using the function from ui/console
ui/console: add methods for allocating, intializing and accessing
QemuDmaBuf
