shaba/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-03-20 06:50:22 +03:00
Code Releases Activity

docs: Lift restriction on running API from the event loop thread

Browse Source 
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 <mprivozn@redhat.com>
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
This commit is contained in:
Michal Privoznik 2021-02-25 15:29:16 +01:00
parent eab7ae6bfe
commit 7fe35dc802
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/drvqemu.html.in
View File

@ -158,8 +158,10 @@ qemu+ssh://root@example.com/system (remote access, SSH tunnelled)
in mind, applications must <strong>NEVER</strong> 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.
</p>
<h2><a id="configFiles">Location of configuration files</a></h2>