From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Cc: marcandre.lureau@redhat.com, dongwon.kim@intel.com, kraxel@redhat.com
Subject: Re: [PATCH for-8.1] vfio/display: Fix missing update to set backing fields
Date: Thu, 17 Aug 2023 00:31:58 +0200 [thread overview]
Message-ID: <a3a6f8ec-ca61-4472-45b4-1077dd27bb52@linaro.org> (raw)
In-Reply-To: <20230816215550.1723696-1-alex.williamson@redhat.com>
On 16/8/23 23:55, Alex Williamson wrote:
> The below referenced commit renames scanout_width/height to
> backing_width/height, but also promotes these fields in various portions
> of the egl interface. Meanwhile vfio dmabuf support has never used the
> previous scanout fields and is therefore missed in the update. This
> results in a black screen when transitioning from ramfb to dmabuf display
> when using Intel vGPU with these features.
Referenced commit isn't trivial. Maybe because it is too late here.
I'd have tried to split it. Anyhow, too late (again).
Is vhost-user-gpu also affected? (see VHOST_USER_GPU_DMABUF_SCANOUT
in vhost_user_gpu_handle_display()).
> Link: https://lists.gnu.org/archive/html/qemu-devel/2023-08/msg02726.html
> Fixes: 9ac06df8b684 ("virtio-gpu-udmabuf: correct naming of QemuDmaBuf size properties")
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
>
> This fixes a regression in dmabuf/EGL support for Intel GVT-g and
> potentially the mbochs mdev driver as well. Once validated by those
> that understand dmabuf/EGL integration, I'd welcome QEMU maintainers to
> take this directly for v8.1 or queue it as soon as possible for v8.1.1.
>
> hw/vfio/display.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/hw/vfio/display.c b/hw/vfio/display.c
> index bec864f482f4..837d9e6a309e 100644
> --- a/hw/vfio/display.c
> +++ b/hw/vfio/display.c
> @@ -243,6 +243,8 @@ static VFIODMABuf *vfio_display_get_dmabuf(VFIOPCIDevice *vdev,
> dmabuf->dmabuf_id = plane.dmabuf_id;
> dmabuf->buf.width = plane.width;
> dmabuf->buf.height = plane.height;
> + dmabuf->buf.backing_width = plane.width;
> + dmabuf->buf.backing_height = plane.height;
> dmabuf->buf.stride = plane.stride;
> dmabuf->buf.fourcc = plane.drm_format;
> dmabuf->buf.modifier = plane.drm_format_mod;
next prev parent reply other threads:[~2023-08-16 22:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 21:55 [PATCH for-8.1] vfio/display: Fix missing update to set backing fields Alex Williamson
2023-08-16 22:31 ` Philippe Mathieu-Daudé [this message]
2023-08-17 16:28 ` Kim, Dongwon
2023-09-04 11:06 ` Marc-André Lureau
2023-09-04 14:11 ` Alex Williamson
2023-09-04 17:00 ` Marc-André Lureau
2023-09-05 15:09 ` Alex Williamson
2023-09-13 19:18 ` Alex Williamson
2023-09-22 9:38 ` Cédric Le Goater
2023-09-22 9:49 ` Michael Tokarev
2023-09-22 11:10 ` Cédric Le Goater
2023-10-03 17:03 ` Michael Tokarev
2023-10-03 21:17 ` Cédric Le Goater
-- strict thread matches above, loose matches on Subject: below --
2023-10-14 9:09 Edmund Raile
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3a6f8ec-ca61-4472-45b4-1077dd27bb52@linaro.org \
--to=philmd@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=dongwon.kim@intel.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).