> -Original Message-
> From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On
> Behalf Of Gerd Hoffmann
> Sent: Tuesday, April 24, 2018 4:16 PM
> To: Zhang, Tina
> Cc: alex.william...@redhat.com; intel-gvt-...@lists.freedesktop.org; qemu-
> de...@nongnu.org; zhen...@
Hi,
> After reviewing this patch-set again, I think we might not need the
> proposed dpy_gfx_switch_surface() any more. The reason I proposed it
> was because I thought gfx.ds is changed to the surface related to
> guest dma-buf framebuffer and we need to switch it with QemuConsole's
> DisplayS
> -Original Message-
> From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On
> Behalf Of Gerd Hoffmann
> Sent: Monday, April 23, 2018 9:12 PM
> To: Zhang, Tina
> Cc: alex.william...@redhat.com; intel-gvt-...@lists.freedesktop.org; qemu-
> de...@nongnu.org; zhen...@l
> +surface = qemu_console_surface(vdev->dpy->con);
> +dpy_gl_scanout_disable(vdev->dpy->con);
> +dpy_gfx_switch_surface(vdev->dpy->con, surface);
Hmm, so you ask which surface is active, then switch to it.
Why?
Maybe you just need a full display update after disabling the gl
scanout?
During guest OS reboot, guest framebuffer is invalid. It will cause
bugs, if the invalid guest framebuffer is still used by host.
This patch is to introduce vfio_display_reset which is invoked
during vfio display reset. This vfio_display_reset function is used
to release the invalid display resour
