From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40298) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1as5NG-0002eu-Q8 for qemu-devel@nongnu.org; Mon, 18 Apr 2016 05:21:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1as5NF-0006Z0-Fn for qemu-devel@nongnu.org; Mon, 18 Apr 2016 05:21:42 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47878) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1as5NF-0006Yv-Ai for qemu-devel@nongnu.org; Mon, 18 Apr 2016 05:21:41 -0400 Message-ID: <1460971298.21910.13.camel@redhat.com> From: Gerd Hoffmann Date: Mon, 18 Apr 2016 11:21:38 +0200 In-Reply-To: <57148C37.90807@suse.de> References: <1460643912-244245-1-git-send-email-agraf@suse.de> <1460647067.18572.31.camel@redhat.com> <570FB743.6060808@suse.de> <1460962415.21910.3.camel@redhat.com> <57148C37.90807@suse.de> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] hid: Extend the event queue size to 1024 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: qemu-devel@nongnu.org, Juan Quintela , Dinar Valeev , Dirk Mueller On Mo, 2016-04-18 at 09:26 +0200, Alexander Graf wrote: >=20 > On 18.04.16 08:53, Gerd Hoffmann wrote: > > Hi, > >=20 > >> Vnc already uses qemu_input_event_send_key_delay today, so I'm not sur= e=20 > >> where things fall apart. > >=20 > > Well, not everywhere. Try the attached patch. > >=20 > > Also worth trying: > > * use xhci instead of ohci (current slof should handle > > kbd-via-xhci fine) > > * use virtio-keyboard (no slof driver yet as far I know, also needs > > a recent linux kernel). >=20 > Ideally I would really like to switch to virtio-input and virtio-gpu for > AArch64, but there are no drivers at all in OVMF. Do you have any plans > to write them? Not investigated yet. There are virtio 1.0 patches in flight for edk2, once they are landed it should be alot simpler (virtio 1.0 is mandatory for virtio-gpu and virtio-input). Keyboard should be easy, it's a simple device. GPU is tricky. Guest is expected to explicitly request display updates. So simply setting up a dump framebuffer, then depending on dirty page tracking for screen updates isn't going to fly. Not sure EFI can handle that. The virtio-vga device has a vga compatibility mode additionally to native virtio. SLOF uses that IIRC. But I think on aarch64 that isn't going to fly either due to the cache coherency issues there. cheers, Gerd