From 7fe35dc802cf50ede7400ad08fc2b1979cf6ec0d Mon Sep 17 00:00:00 2001 From: Michal Privoznik Date: Thu, 25 Feb 2021 15:29:16 +0100 Subject: [PATCH] docs: Lift restriction on running API from the event loop thread Since v6.2.0-rc1~238 (and friends) QMP processing was moved to a per-domain thread. Therefore, it is now safe to call APIs from the event loop thread (e.g. just like qemu shim is doing in qemuShimEventLoop(). However, it is still important to let the event loop run after each API call (obviously). Signed-off-by: Michal Privoznik Reviewed-by: Andrea Bolognani --- docs/drvqemu.html.in | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/drvqemu.html.in b/docs/drvqemu.html.in index a784f5768c..375c1b0352 100644 --- a/docs/drvqemu.html.in +++ b/docs/drvqemu.html.in @@ -158,8 +158,10 @@ qemu+ssh://root@example.com/system (remote access, SSH tunnelled) in mind, applications must NEVER invoke API calls from the event loop thread itself, only other threads. Not following this rule will lead to deadlocks in the API. - This restriction is intended to be lifted in a future release - of libvirt, once QMP processing moves to a dedicated thread. + This restriction was lifted starting from 6.2.0 release, when + QMP processing moved to a dedicated thread. However, it is + important to let the event loop run after each API call, even + the ones made from the event loop thread itself.

Location of configuration files

-- 2.47.2