summaryrefslogtreecommitdiffstats
path: root/src/launch-libvirt.c
diff options
context:
space:
mode:
authorRichard W.M. Jones <rjones@redhat.com>2012-10-15 21:35:13 +0100
committerRichard W.M. Jones <rjones@redhat.com>2012-10-15 22:38:27 +0100
commit99bd15ad0e900ce16fe16d2a58b4d6f8ba38a0fe (patch)
treea9213dcd076b9e8c32a6f82be0e36ce960e8b5b7 /src/launch-libvirt.c
parent3d46f7dc038f87e00a27e9f294d4115436f1ff23 (diff)
downloadlibguestfs-99bd15ad0e900ce16fe16d2a58b4d6f8ba38a0fe.tar.gz
libguestfs-99bd15ad0e900ce16fe16d2a58b4d6f8ba38a0fe.tar.xz
libguestfs-99bd15ad0e900ce16fe16d2a58b4d6f8ba38a0fe.zip
generator: Add 'blocking' flag to marking blocking (long-running) functions.
In languages like Python where we release a global lock around long-running libguestfs functions, it is also useful to *not* release this lock for small, non-blocking functions. Therefore mark all functions with a 'blocking' boolean flag. It defaults to true, and is true by definition for all daemon functions. For non-daemon functions, I have classified them manually. Only when the blocking flag is set do we generate the code to release and reacquire the lock around libguestfs calls.
Diffstat (limited to 'src/launch-libvirt.c')
0 files changed, 0 insertions, 0 deletions