|
From: | Markus Armbruster |
Subject: | Re: [Qemu-devel] [PATCH v3 2/6] monitor: accept chardev input from iothread |
Date: | Wed, 05 Dec 2018 09:17:06 +0100 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Marc-André Lureau <address@hidden> writes: > Chardev backends may not handle safely IO events from concurrent > threads (they are not thread-safe in general, only the write path is Suggest "may not handle I/O events from concurrent threads safely". > since commit > 9005b2a7589540a3733b3abdcfbccfe7746cd1a1). Better to > wake up the chardev from the monitor IO thread if it's being used as > the chardev context. > > Unify code paths by using a BH in all cases. > > Drop the now redundant aio_notify() call. > > Simplify the condition, based on mon->use_io_thread (only QMP so far). Suggest Clean up control flow not to rely on mon->use_io_thread implying monitor_is_qmp(mon). > Signed-off-by: Marc-André Lureau <address@hidden> > Reviewed-by: Peter Xu <address@hidden> Happy to improve the commit message in my tree. Preferably with commit message improvements: Reviewed-by: Markus Armbruster <address@hidden>
[Prev in Thread] | Current Thread | [Next in Thread] |