[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [PATCH] Kick io-thread on qemu_chr_accept_input
From: |
Jan Kiszka |
Subject: |
[Qemu-devel] [PATCH] Kick io-thread on qemu_chr_accept_input |
Date: |
Fri, 16 Mar 2012 13:25:55 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 |
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 <address@hidden>
---
/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
- [Qemu-devel] [PATCH] Kick io-thread on qemu_chr_accept_input,
Jan Kiszka <=