From: "Michael S. Tsirkin" <mst@redhat.com>
To: marcandre.lureau@redhat.com
Cc: qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [PATCH] virtio-gpu: add a FIXME for virtio_gpu_load()
Date: Thu, 18 May 2023 17:35:09 -0400 [thread overview]
Message-ID: <20230518173438-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230515132518.1025853-1-marcandre.lureau@redhat.com>
On Mon, May 15, 2023 at 05:25:18PM +0400, marcandre.lureau@redhat.com wrote:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> It looks like the virtio_gpu_load() does not compute and set the offset,
> the same way virtio_gpu_set_scanout() does. This probably results in
> incorrect display until the scanout/framebuffer is updated again, I
> guess we should fix it, although I haven't checked this yet.
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
I guess it's a way to ping Gerd ;)
Better to just fix it though, no?
> ---
> hw/display/virtio-gpu.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/display/virtio-gpu.c b/hw/display/virtio-gpu.c
> index 66ac9b6cc5..66cddd94d9 100644
> --- a/hw/display/virtio-gpu.c
> +++ b/hw/display/virtio-gpu.c
> @@ -1289,6 +1289,7 @@ static int virtio_gpu_load(QEMUFile *f, void *opaque, size_t size,
> /* load & apply scanout state */
> vmstate_load_state(f, &vmstate_virtio_gpu_scanouts, g, 1);
> for (i = 0; i < g->parent_obj.conf.max_outputs; i++) {
> + /* FIXME: should take scanout.r.{x,y} into account */
> scanout = &g->parent_obj.scanout[i];
> if (!scanout->resource_id) {
> continue;
> --
> 2.40.1
next prev parent reply other threads:[~2023-05-18 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 13:25 [PATCH] virtio-gpu: add a FIXME for virtio_gpu_load() marcandre.lureau
2023-05-18 21:35 ` Michael S. Tsirkin [this message]
2023-05-24 10:50 ` Marc-André Lureau
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=20230518173438-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.