[libvirt] [PULL 11/12] dmabuf: add y0_top, pass it to spice

2018-08-27 Thread Gerd Hoffmann
From: Marc-André Lureau Some scanouts during boot are top-down without it. y0_top is set from VHOST_USER_GPU_DMABUF_SCANOUT code path in the last patch of this series. In current QEMU code base, only vfio/display uses dmabuf API. But the VFIO query interface doesn't provide or need that detail

[libvirt] [PULL 11/12] dmabuf: add y0_top, pass it to spice

2018-08-23 Thread Gerd Hoffmann
From: Marc-André Lureau Some scanouts during boot are top-down without it. y0_top is set from VHOST_USER_GPU_DMABUF_SCANOUT code path in the last patch of this series. In current QEMU code base, only vfio/display uses dmabuf API. But the VFIO query interface doesn't provide or need that detail

[libvirt] [PULL 11/12] dmabuf: add y0_top, pass it to spice

2018-08-21 Thread Gerd Hoffmann
From: Marc-André Lureau Some scanouts during boot are top-down without it. y0_top is set from VHOST_USER_GPU_DMABUF_SCANOUT code path in the last patch of this series. In current QEMU code base, only vfio/display uses dmabuf API. But the VFIO query interface doesn't provide or need that detail

[libvirt] [PULL 11/12] dmabuf: add y0_top, pass it to spice

2018-08-21 Thread Gerd Hoffmann
From: Marc-André Lureau Some scanouts during boot are top-down without it. y0_top is set from VHOST_USER_GPU_DMABUF_SCANOUT code path in the last patch of this series. In current QEMU code base, only vfio/display uses dmabuf API. But the VFIO query interface doesn't provide or need that detail