All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Marc-André Lureau" <marcandre.lureau@gmail.com>
To: QEMU <qemu-devel@nongnu.org>, Gerd Hoffmann <kraxel@redhat.com>
Cc: Dave Airlie <airlied@gmail.com>
Subject: [Qemu-devel] virtio-gpu: cursor update not in sync with resource update
Date: Mon, 14 Sep 2015 14:40:08 +0200	[thread overview]
Message-ID: <CAJ+F1CKywA+Y9-aJ4oK=j72VZq6BS7CX_SKqWrfZCK3o9TOWog@mail.gmail.com> (raw)

Hi

Afaik, the goal of the seperate cursor queue is to update cursor
quickly (probably to give good input responsiveness). However, the
VIRTIO_GPU_CMD_UPDATE_CURSOR references a surface that is uploaded via
the ctrl queue. The same resource id may be reused for cursor update.
But there is no synchronization between the two queues. So often, the
cursor set results in last update being shown. Should the kernel wait
for the update to finish? But then why having 2 different queues?
Should the update be done on the cursor queue instead? or should the
different cursor be cached (with different id) and qemu to do the
synchronization?

-- 
Marc-André Lureau

             reply	other threads:[~2015-09-14 12:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 12:40 Marc-André Lureau [this message]
2015-09-14 14:06 ` [Qemu-devel] virtio-gpu: cursor update not in sync with resource update Gerd Hoffmann
2015-09-14 15:17   ` Marc-André Lureau
2015-09-14 21:08     ` Dave Airlie
2015-09-14 21:14       ` Marc-André Lureau
2015-09-14 21:18         ` Dave Airlie
2015-09-15  6:20           ` Gerd Hoffmann

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='CAJ+F1CKywA+Y9-aJ4oK=j72VZq6BS7CX_SKqWrfZCK3o9TOWog@mail.gmail.com' \
    --to=marcandre.lureau@gmail.com \
    --cc=airlied@gmail.com \
    --cc=kraxel@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.