Home
last modified time | relevance | path

Searched refs:locks (Results 1 – 25 of 40) sorted by relevance

12

/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/
H A Dpython3-fasteners_0.19.bb1 SUMMARY = "A python package that provides useful locks."
/openbmc/openbmc-test-automation/openpower/ext_interfaces/
H A Dtest_lock_management.robot29 [Documentation] Acquire and release different read locks.
63 [Documentation] Acquire and release read and write locks after reboot.
77 [Documentation] Acquire and release read, write locks in loop.
123 [Documentation] Release all valid locks.
183 [Documentation] Failed to release locks from another session.
192 [Documentation] Acquire lock and after reboot the locks are removed as no persistency
300 [Documentation] If session does not acquire locks then get lock should return
613 [Documentation] Get locks list.
623 ${locks}= Evaluate json.loads('''${resp.text}''') json
625 RETURN ${locks["Records"]}
[all …]
/openbmc/phosphor-fan-presence/control/json/
H A Dzone.cpp538 const auto& locks = fan->getLockedTargets(); in dump() local
539 if (!locks.empty()) in dump()
541 lockedTargets[fan->getName()] = locks; in dump()
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/vlock/
H A Dvlock_2.2.3.bb3 than a sophisticated remote one. vlock is a program that locks one or more \
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/sanlock/
H A Dsanlock_4.0.0.bb6 Internally, the sanlock daemon manages locks using two disk-based \
/openbmc/openbmc/meta-openembedded/meta-networking/files/waf-cross-answers/
H A Dcross-answers-aarch64.txt39 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-mips64el.txt39 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-powerpc.txt40 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-aarch64_be.txt39 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-mips.txt40 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-riscv32.txt40 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-powerpc64.txt40 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-powerpc64le.txt40 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-armeb.txt40 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-x86_64.txt39 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-mipsel.txt40 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-i686.txt40 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-mips64.txt39 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-riscv64.txt39 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-i586.txt40 Checking whether fcntl lock supports open file description locks: OK
H A Dcross-answers-arm.txt40 Checking whether fcntl lock supports open file description locks: OK
/openbmc/openbmc/poky/meta/lib/oe/
H A Dprservice.py81 with open(df, "a") as f, bb.utils.fileslocked(["%s.lock" % df]) as locks:
/openbmc/openbmc/poky/meta/recipes-extended/lighttpd/
H A Dlighttpd_1.4.79.bb37 PACKAGECONFIG[webdav-locks] = "-Dwith_webdav_locks=enabled,-Dwith_webdav_locks=disabled,util-linux"
/openbmc/qemu/docs/devel/
H A Drcu.rst26 for example, reader-writer locks. It is so much more scalable that
81 the updater releases any locks it may hold before calling
215 Many patterns using read-writer locks translate directly to RCU, with
305 locks::
/openbmc/openbmc/poky/documentation/dev-manual/
H A Dbblock.rst97 This produces architecture specific locks and reminds user that some tasks

12