]> git.ipfire.org Git - thirdparty/libvirt.git/commit
m4: Check for sanlock_write_lockspace
authorMichal Privoznik <mprivozn@redhat.com>
Thu, 15 Sep 2016 08:45:26 +0000 (10:45 +0200)
committerMichal Privoznik <mprivozn@redhat.com>
Thu, 29 Sep 2016 14:59:11 +0000 (16:59 +0200)
commit2bca7cec0ba9e861edb245f20d99d5b6fd22f760
tree9138ce7f276e866324112bf250bb0b5d0d55d4ee
parent78da4296a614c5d8a777ea2de8380ea11208e59b
m4: Check for sanlock_write_lockspace

Currently, we are checking for sanlock_add_lockspace_timeout
which is good for now. But in a subsequent patch we are going to
use sanlock_write_lockspace (which sets an initial value for io
timeout for sanlock). Now, there is no reason to check for both
functions in sanlock library as the sanlock_write_lockspace was
introduced in 2.7 release and the one we are currently checking
for in the 2.5 release. Therefore it is safe to assume presence
of sanlock_add_lockspace_timeout when sanlock_write_lockspace
is detected.

Moreover, the macro for conditional compilation is renamed to
HAVE_SANLOCK_IO_TIMEOUT (as it now encapsulates two functions).

Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
m4/virt-sanlock.m4
src/locking/lock_driver_sanlock.c