[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] RFC: running the user interface in a thread ...
From: |
Gerd Hoffmann |
Subject: |
Re: [Qemu-devel] RFC: running the user interface in a thread ... |
Date: |
Thu, 21 Jan 2016 11:39:20 +0100 |
Hi,
> That sounds good in theory (but see below) since AioContext integrates
> with the glib main loop because it is a GSource. QEMU code should use
> AioContext where we have high resolution timers and APIs for file
> descriptor, EventNotifier, and BH.
Sounds good.
> Use BH or EventNotifier instead. BH has optimizations to avoid syscalls
> where possible while EventNotifier is just a plain eventfd/pipe
> (requires a write() syscall for each notification).
How does BH signaling work? I know I can qemu_bh_schedule from !main
thread to kick BH in main thread context. The other way around works
using aio_bh_new + aio_bh_call I guess?
thanks,
Gerd
Re: [Qemu-devel] RFC: running the user interface in a thread ..., Kevin Wolf, 2016/01/19
Re: [Qemu-devel] RFC: running the user interface in a thread ..., Daniel P. Berrange, 2016/01/19
Re: [Qemu-devel] RFC: running the user interface in a thread ..., Dave Airlie, 2016/01/21