Re: [Qemu-devel] [PATCH] Kick io-thread on qemu_chr_accept_input

2012-03-29 Thread Jan Kiszka
On 2012-03-16 14:18, Jan Kiszka wrote: On 2012-03-16 14:16, Anthony Liguori wrote: On 03/16/2012 07:25 AM, Jan Kiszka wrote: 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

[Qemu-devel] [PATCH] Kick io-thread on qemu_chr_accept_input

2012-03-16 Thread Jan Kiszka
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.

Re: [Qemu-devel] [PATCH] Kick io-thread on qemu_chr_accept_input

2012-03-16 Thread Anthony Liguori
On 03/16/2012 07:25 AM, Jan Kiszka wrote: 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

Re: [Qemu-devel] [PATCH] Kick io-thread on qemu_chr_accept_input

2012-03-16 Thread Jan Kiszka
On 2012-03-16 14:16, Anthony Liguori wrote: On 03/16/2012 07:25 AM, Jan Kiszka wrote: 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.