Home
last modified time | relevance | path

Searched full:holding (Results 1 – 25 of 125) sorted by relevance

12345

/Documentation/locking/
Drobust-futex-ABI.rst11 The interesting data as to what futexes a thread is holding is kept on a
65 of the thread holding the lock in the bottom 30 bits. See further
88 specified 'offset'. Should a thread die while holding any such locks,
130 thread currently holding such a lock, if any, is marked with the threads
169 lock owner died holding the lock.
Dww-mutex-design.rst39 If the transaction holding the lock is younger, the locking transaction waits.
40 If the transaction holding the lock is older, the locking transaction backs off
43 If the transaction holding the lock is younger, the locking transaction
44 wounds the transaction holding the lock, requesting it to die.
45 If the transaction holding the lock is older, it waits for the other
237 and edges can only be changed when holding the locks of all involved nodes. w/w
Drobust-futexes.rst30 "Robustness" is about dealing with crashes while holding a lock: if a
31 process exits prematurely while holding a pthread_mutex_t lock that is
32 also shared with some other process (e.g. yum segfaults while holding a
90 robust locks that userspace is holding (maintained by glibc) - which
Dlocktypes.rst151 readers, a preempted low-priority reader will continue holding its lock,
252 - Tasks holding a spinlock_t do not migrate. Non-PREEMPT_RT kernels
314 readers, a preempted low-priority reader will continue holding its lock,
485 while holding normal non-raw spinlocks because they do not disable
526 per-CPU spinlock_t means that they cannot be acquired while holding a raw
/Documentation/devicetree/bindings/input/
Dinput-reset.txt5 sysrq driver. Upon holding the keys for a specified amount of time (if
/Documentation/devicetree/bindings/dma/
Dmoxa,moxart-dma.txt11 - #dma-cells : Should be 1, a single cell holding a line request number
/Documentation/devicetree/bindings/clock/
Dmoxa,moxart-clock.txt8 by reading registers holding multiplier and divisor information.
/Documentation/core-api/
Dkref.rst72 holding a valid pointer, it is safe to do this without
76 without already holding a valid pointer, it must serialize access
129 already holding a pointer.
173 holding a valid pointer. You must add a mutex (or some other lock).
/Documentation/userspace-api/media/v4l/
Dstreaming-par.rst30 contains a union holding separate parameters for input and output
/Documentation/admin-guide/device-mapper/
Dera.rst24 metadata dev fast device holding the persistent metadata
25 origin dev device holding data blocks that may change
/Documentation/devicetree/bindings/net/
Dsocionext,synquacer-netsec.yaml23 - description: EEPROM holding the MAC address and microengine firmware
/Documentation/devicetree/bindings/display/panel/
Dolimex,lcd-olinuxino.yaml21 - AT24C16C EEPROM holding panel identification and timing requirements
/Documentation/filesystems/
Ddirectory-locking.rst89 dcache trees. Lookup is already holding the parent locked. If alias is
102 all we change is the view in dcache. Moreover, holding a directory locked
103 exclusive prevents such changes involving its children and holding the
245 rename holding the lock on parent of source and trying to lock its
/Documentation/devicetree/bindings/rtc/
Dqcom-pm8xxx-rtc.yaml46 four-byte nvmem cell holding a little-endian offset from the Unix
/Documentation/kernel-hacking/
Dlocking.rst111 spinlock, but you may block holding a mutex. If you can't lock a mutex,
304 - Avoid holding spinlock for more than 5 lines of code and across any
357 lock when some other thread is holding the lock. You should acquire the
405 /* Must be holding cache_lock */
418 /* Must be holding cache_lock */
427 /* Must be holding cache_lock */
645 /* Must be holding cache_lock */
691 now sleep holding the object (eg. to copy_to_user() to
760 /* Must be holding cache_lock */
1020 going to be waiting while someone else is holding a lock. Second is the
[all …]
/Documentation/devicetree/bindings/leds/
Dti,tca6507.yaml14 7 separate lines either by holding them low, or by pulsing them with modulated
/Documentation/driver-api/
Dio-mapping.rst74 If you need to sleep while holding a mapping, you can use the regular
/Documentation/driver-api/pm/
Dcpuidle.rst86 processor holding the given CPU can be asked to enter).
113 Called to select an idle state for the processor holding the (logical)
175 idle state represented by the struct cpuidle_state object holding it, this
/Documentation/power/
Dswsusp-and-swap-files.rst18 filesystem holding the swap file to be mounted, and if this filesystem is
Ds2ram.rst42 holding the power button down, and look at the dmesg output for things
/Documentation/security/
Dsak.rst51 incorrectly holding /dev/console open. Be sure to complain to your
/Documentation/ABI/testing/
Dsysfs-driver-hid-ntrig19 number of empty frames. By holding off on deactivation for a few
/Documentation/userspace-api/
Diommufd.rst145 - struct io_pagetable holding the IOVA map
150 - struct xarray pinned_pfns holding a list of pages pinned by in-kernel users
/Documentation/userspace-api/netlink/
Dspecs.rst337 or both of these properties, each holding a :ref:`attr_list`.
343 or both of these properties, each holding a :ref:`attr_list`.
349 (possibly the same as the operation holding this property) which shares
/Documentation/bpf/
Dprog_sk_lookup.rst60 in a map holding sockets, such as ``SOCKMAP`` or ``SOCKHASH``, and passes a

12345