Home
last modified time | relevance | path

Searched refs:locking (Results 1 – 25 of 139) sorted by relevance

123456

/external/valgrind/main/helgrind/tests/
Dt2t_laog.stdout.exp13 locking level 0
14 locking level 1
15 locking level 2
16 locking level 3
17 locking level 4
18 locking level 5
19 locking level 6
20 locking level 7
21 locking level 8
22 locking level 9
[all …]
Dtc15_laog_lockdel.stderr.exp29 so a second locking sequence 2 -> 1 should now be OK.
/external/chromium_org/third_party/sqlite/src/doc/
Dvfs-shm.txt11 The wal-index file has a similar locking hierarchy implemented using
28 The meanings of the various wal-index locking states is as follows:
60 the wal-index locking states, though with a reduction in concurrency.
61 For example, an implemention might implement only exclusive locking,
104 those locking states in response to READ and CHECKPOINT requests,
130 transitions among the 7 locking states will never occur.
/external/valgrind/main/memcheck/tests/
Dfile_locking.stderr.exp2 parent: file locking attempt succeeded.
/external/valgrind/main/drd/tests/
Dtc15_laog_lockdel.stderr.exp5 so a second locking sequence 2 -> 1 should now be OK.
Dtrylock.stderr.exp9 Recursive writer locking not allowed: rwlock 0x.........
/external/chromium_org/ppapi/api/
Dppb_mouse_lock.idl8 * locking the target of mouse events to a specific module instance.
19 * This interface provides a way of locking the target of mouse events to a
/external/chromium_org/third_party/mesa/src/src/glx/apple/
DTODO24 Where 2 threads are doing the same sort of path of create and destroy. The locking should protect
/external/mesa3d/src/glx/apple/
DTODO24 Where 2 threads are doing the same sort of path of create and destroy. The locking should protect
/external/chromium_org/third_party/sqlite/src/test/
Dlock5.test34 # Disable the proxy locking for these tests
118 # Make sure we are not accidentally using the dotfile locking scheme.
Djournal1.test23 # manditory file locking which breaks the file copy command.
Dexclusive.test227 # Changing the locking-mode does not release any locks.
236 # After changing the locking mode, accessing the db releases locks.
403 # sqlite uses 1 (proxy locking adds the conch and the local lock)
Dmanydb.test24 # sqlite uses 3 (proxy locking adds the conch and the local lock)
Dlock2.test22 # Simple locking test case:
Dcache.test44 # At one point, repeatedly locking and unlocking the cache was causing
Dpermutations.test412 # Run some tests in exclusive locking mode.
415 Run tests in exclusive locking mode.
423 # Run some tests in exclusive locking mode with truncated journals.
426 Run tests in exclusive locking mode and truncate journal mode.
/external/libusb/
DNEWS20 * Bug fixes including transfer locking to fix some potential threading races
/external/chromium_org/third_party/sqlite/src/ext/async/
DREADME.txt85 If file-locking is enabled (it is enabled by default), then connections
107 File-locking may be disabled at runtime using the sqlite3async_control()
111 connections attempt to access the same database file when file-locking
/external/qemu/distrib/sdl-1.2.15/test/
DREADME22 testlock Hacked up test of multi-threading and locking
/external/chromium_org/third_party/tcmalloc/vendor/
DTODO11 4) Port to non-x86 architectures (locking code in spinlock is x86-specific)
/external/mesa3d/src/mesa/swrast/
DNOTES53 for locking and setting the read buffer.
/external/chromium_org/third_party/mesa/src/src/mesa/swrast/
DNOTES53 for locking and setting the read buffer.
/external/chromium_org/third_party/mesa/src/src/mesa/swrast_setup/
DNOTES62 point rasterization, these are necessary to provide locking hooks for
/external/mesa3d/src/mesa/swrast_setup/
DNOTES62 point rasterization, these are necessary to provide locking hooks for
/external/libcap-ng/libcap-ng-0.7/
DChangeLog71 - Make locking a noop in capng_change_id for the moment

123456