From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59343) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZbT3S-0008A0-Fk for qemu-devel@nongnu.org; Mon, 14 Sep 2015 08:40:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZbT3M-0005K6-Tn for qemu-devel@nongnu.org; Mon, 14 Sep 2015 08:40:18 -0400 Received: from mail-oi0-x229.google.com ([2607:f8b0:4003:c06::229]:36221) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZbT3M-0005Ht-P5 for qemu-devel@nongnu.org; Mon, 14 Sep 2015 08:40:12 -0400 Received: by oibi136 with SMTP id i136so75834364oib.3 for ; Mon, 14 Sep 2015 05:40:08 -0700 (PDT) MIME-Version: 1.0 Date: Mon, 14 Sep 2015 14:40:08 +0200 Message-ID: From: =?UTF-8?B?TWFyYy1BbmRyw6kgTHVyZWF1?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] virtio-gpu: cursor update not in sync with resource update List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: QEMU , Gerd Hoffmann Cc: Dave Airlie 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? --=20 Marc-Andr=C3=A9 Lureau