From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:60030) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S8WEc-0007tP-41 for qemu-devel@nongnu.org; Fri, 16 Mar 2012 08:26:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S8WEM-0003YT-Mq for qemu-devel@nongnu.org; Fri, 16 Mar 2012 08:26:17 -0400 Received: from goliath.siemens.de ([192.35.17.28]:29526) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S8WEM-0003Y8-Ct for qemu-devel@nongnu.org; Fri, 16 Mar 2012 08:26:02 -0400 Message-ID: <4F633153.9030004@siemens.com> Date: Fri, 16 Mar 2012 13:25:55 +0100 From: Jan Kiszka MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] [PATCH] Kick io-thread on qemu_chr_accept_input List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori , qemu-devel Cc: Marek Vasut , Paolo Bonzini Once a chr frontend is able to receive input again, we need to inform the io-thread about this fact. Otherwise, main_loop_wait may continue to select without the related backend file descriptor in its set. This can cause high input latencies if only low-rate events arrive otherwise. Signed-off-by: Jan Kiszka --- /me wonders if a similar issue explains the slirp slowness under KVM with in-kernel irqchip enabled. Need to check... qemu-char.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/qemu-char.c b/qemu-char.c index 9a5be75..a589a84 100644 --- a/qemu-char.c +++ b/qemu-char.c @@ -177,6 +177,7 @@ void qemu_chr_accept_input(CharDriverState *s) { if (s->chr_accept_input) s->chr_accept_input(s); + qemu_notify_event(); } void qemu_chr_fe_printf(CharDriverState *s, const char *fmt, ...) -- 1.7.3.4