Home
last modified time | relevance | path

Searched full:locks (Results 1 – 25 of 119) sorted by relevance

12345

/openbmc/qemu/scripts/
H A Danalyse-locks-simpletrace.py14 "A simpletrace Analyser for checking locks."
17 self.locks = 0
24 self.mutex_records[mutex] = {"locks": 0,
35 self.locks += 1
37 rec["locks"] += 1
74 print ("Total locks: %d, locked: %d, unlocked: %d" %
75 (analyser.locks, analyser.locked, analyser.unlocks))
79 key=lambda k_v: k_v[1]["locks"]):
80 print ("Lock: %#x locks: %d, locked: %d, unlocked: %d" %
81 (key, val["locks"], val["locked"], val["unlocked"]))
[all …]
/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.
122 Verify Release Of Valid Locks
123 [Documentation] Release all valid locks.
125 [Template] Acquire And Release Multiple Locks
183 [Documentation] Failed to release locks from another session.
192 [Documentation] Acquire lock and after reboot the locks are removed as no persistency
299 Get Empty Lock Records For Session Where No Locks Acquired
300 [Documentation] If session does not acquire locks then get lock should return
[all …]
/openbmc/qemu/tests/qemu-iotests/
H A D1824 # Test image locking for POSIX locks
62 -e '/locks can be lost unexpectedly/d'
159 # When quitting qemu, it will try to drop its locks on the test image.
/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/qemu/util/
H A Dqht.c20 * via a seqlock; iterators acquire all bucket locks and therefore can be
155 * Under TSAN, we use striped locks instead of one lock per bucket chain.
157 * 64 locks are held (this is a hardcoded limit in TSAN).
158 * When resizing a QHT we grab all the buckets' locks, which can easily
159 * go over TSAN's limit. By using striped locks, we avoid this problem.
179 * @tsan_bucket_locks: Array of striped locks to be used only under TSAN.
253 * When using striped locks (i.e. under TSAN), we have to be careful not
311 /* acquire all bucket locks from a map */
336 * @map should be the value read before acquiring the lock (or locks).
345 * Grab all bucket locks, and set @pmap after making sure the map isn't stale.
[all …]
/openbmc/qemu/accel/tcg/
H A Dinternal-common.h113 * via locks for consistency. In user-mode emulation access to the
115 * In !user-mode we use per-page locks.
/openbmc/qemu/tests/qemu-iotests/tests/
H A Dmirror-top-perms63 external process could access the image unhindered by locks.
65 take its own locks, e.g. a format driver.)
/openbmc/qemu/include/hw/i386/
H A Dx86.h91 * Ratelimit enforced on detected bus locks in guest.
93 * which means no limitation on the guest's bus locks.
/openbmc/phosphor-host-ipmid/user_channel/
H A Dshadowlock.hpp30 /** @brief Default constructor that just locks the shadow file */
/openbmc/phosphor-fan-presence/control/json/actions/
H A Doverride_fan_target.hpp32 * This action locks fans at configured targets when the configured `count`
36 * the next-highest target remaining in its list of locks.
/openbmc/phosphor-user-manager/
H A Dshadowlock.hpp34 /** @brief Default constructor that just locks the shadow file */
/openbmc/phosphor-fan-presence/control/json/
H A Dfan.hpp134 * Removes the provided target lock from the list of locks. Fan will unlock
135 * (become eligible for setTarget()) when all locks are removed from the
H A Dfan.cpp149 // if multiple locks, take highest, else allow only the in lockTarget()
175 // if additional locks, re-lock at next-highest target in unlockTarget()
/openbmc/qemu/include/qemu/
H A Dlockable.h79 * to a function that can operate with locks of any kind, or
99 * to a function that can operate with locks of any kind.
H A Dcoroutine.h190 * Read locks the CoRwlock. If the lock cannot be taken immediately because
197 * Write Locks the CoRwlock from a reader. This is a bit more efficient than
214 * Write Locks the mutex. If the lock cannot be taken immediately because
/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/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

12345