From patchwork Fri Mar 16 12:25:55 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Kick io-thread on qemu_chr_accept_input Date: Fri, 16 Mar 2012 02:25:55 -0000 From: Jan Kiszka X-Patchwork-Id: 147195 Message-Id: <4F633153.9030004@siemens.com> 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, ...)