From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56896) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aqj1k-0007Zc-RP for qemu-devel@nongnu.org; Thu, 14 Apr 2016 11:17:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aqj1i-0007jg-5e for qemu-devel@nongnu.org; Thu, 14 Apr 2016 11:17:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38204) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aqj1i-0007jS-0e for qemu-devel@nongnu.org; Thu, 14 Apr 2016 11:17:50 -0400 Message-ID: <1460647067.18572.31.camel@redhat.com> From: Gerd Hoffmann Date: Thu, 14 Apr 2016 17:17:47 +0200 In-Reply-To: <1460643912-244245-1-git-send-email-agraf@suse.de> References: <1460643912-244245-1-git-send-email-agraf@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 Do, 2016-04-14 at 16:25 +0200, Alexander Graf wrote: > We can currently buffer up to 16 events in our event queue for input > devices. While it sounds like 16 events backlog for everyone should > be enough, our automated testing tools (OpenQA) manage to easily > type faster than our guests can handle. IMO you should fix OpenQA to type slower then. Real hardware is made for human typing speeds. qemu emulates real hardware. Typing insane fast is going to cause problems because the hardware interfaces are not designed for that. Note the ps/2 keyboard has only a 16 byte queue too. Used to be 256 bytes, but that caused problems because this diverges from real hardware (see commit 2858ab09e6f708e381fc1a1cc87e747a690c4884 for all the details). Note that the generic input code has support for slow typing already (see qemu_input_event_send_key_delay in ui/input.c). That queue will (a) work for all keyboard devices and (b) isn't visible to the guest, so using that might be a reasonable option if you can't put the delay logic into OpenQA. How to you feed the guest with keystrokes? monitor? vnc? cheers, Gerd