Searched +full:lock +full:- +full:offset (Results 1 – 25 of 55) sorted by relevance
123
| /Documentation/locking/ |
| D | robust-futex-ABI.rst | 48 kernel, then it can actually have two such structures - one using 32 bit
56 pointer to a single linked list of 'lock entries', one per lock,
58 to itself, 'head'. The last 'lock entry' points back to the 'head'.
60 The second word, called 'offset', specifies the offset from the
61 address of the associated 'lock entry', plus or minus, of what will
62 be called the 'lock word', from that 'lock entry'. The 'lock word'
63 is always a 32 bit word, unlike the other words above. The 'lock
65 of the thread holding the lock in the bottom 30 bits. See further
69 the address of the 'lock entry', during list insertion and removal,
73 Each 'lock entry' on the single linked list starting at 'head' consists
[all …]
|
| /Documentation/netlink/specs/ |
| D | dpll.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
8 -
16 -
20 -
23 render-max: true
24 -
26 name: lock-status
28 provides information of dpll device lock status, valid values for
31 -
37 -
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | arm,syscon-icst.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/arm,syscon-icst.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linusw@kernel.org>
19 an ICST clock request after a write to the 32 bit register at an offset
22 writing a special token to another offset in the system controller.
25 connects the low 8 bits of the VDW (missing one bit), hard-wires RDW to
26 different values and sometimes also hard-wires the output divider. They
38 integratorap-cm
[all …]
|
| /Documentation/ABI/testing/ |
| D | debugfs-tpmi | 1 What: /sys/kernel/debug/tpmi-<n>/pfs_dump
8 tpmi_id, number of entries, entry size, offset, vsec offset, lock status
12 What: /sys/kernel/debug/tpmi-<n>/tpmi-id-<n>/mem_dump
20 What: /sys/kernel/debug/tpmi-<n>/tpmi-id-<n>/mem_write
25 Allows to write at any offset. It doesn't check for Read/Write access
26 as hardware will not allow to write at read-only memory. This write is
27 at offset multiples of 4. The format is instance,offset,contents.
33 What: /sys/kernel/debug/tpmi-<n>/plr/domain<n>/status
|
| /Documentation/networking/ |
| D | strparser.rst | 1 .. SPDX-License-Identifier: GPL-2.0
126 The skb->cb in the input skb is a struct strp_msg. Only
127 the offset field is relevant in parse_msg and gives the offset
135 -ESTRPIPE current message should not be processed by the
146 -ESTRPIPE and the stream parser had previously read some bytes for
152 void (*lock)(struct strparser *strp)
154 The lock callback is called to lock the strp structure when
164 The unlock callback is called to release the lock obtained
165 by the lock callback. In receive callback mode the default
179 The skb->cb in the input skb is a struct strp_msg. This
[all …]
|
| D | filter.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 .. _networking-filter:
10 ------
17 ------------
24 BPF allows a user-space program to attach a filter onto any socket and
44 SO_LOCK_FILTER option allows to lock the filter attached to a socket. Once
46 setup a socket, attach a filter, lock it then drop privileges and be
49 The biggest user of this construct might be libpcap. Issuing a high-level
50 filter command like `tcpdump -i em1 port 22` passes through the libpcap
52 via SO_ATTACH_FILTER to the kernel. `tcpdump -i em1 port 22 -ddd`
[all …]
|
| /Documentation/core-api/ |
| D | this_cpu_ops.rst | 14 this_cpu operations add a per cpu variable offset to the processor
19 the offset and the operation on the data. Therefore it is not
24 Read-modify-write operations are of particular interest. Frequently
29 lock prefix and the associated latency penalty.
31 Access to the variable without the lock prefix is not synchronized but
65 ------------------------------------
94 The above results in the following single instruction (no lock prefix!)::
128 ------------------
134 Takes the offset of a per cpu variable (&x !) and returns the address
138 available. Instead, the offset of the local per cpu area is simply
[all …]
|
| D | swiotlb.rst | 1 .. SPDX-License-Identifier: GPL-2.0
19 These APIs use the device DMA attributes and kernel-wide settings to determine
30 ---------------
33 only provide 32-bit DMA addresses. By allocating bounce buffer memory below
40 directed to guest memory that is unencrypted. CoCo VMs set a kernel-wide option
54 IOMMU access control is per-granule, the untrusted device can gain access to
60 ------------------
85 ------------------------------
89 pre-allocated at boot time (but see Dynamic swiotlb below). Because swiotlb
93 The need to pre-allocate the default swiotlb pool creates a boot-time tradeoff.
[all …]
|
| /Documentation/driver-api/ |
| D | ptp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
18 - Set time
19 - Get time
20 - Shift the clock by a given offset atomically
21 - Adjust clock frequency
24 - Time stamp external events
25 - Period output signals configurable from user space
26 - Low Pass Filter (LPF) access from user space
27 - Synchronization of the Linux system time via the PPS subsystem
65 ancillary feature, then the driver should just return -EOPNOTSUPP
[all …]
|
| /Documentation/filesystems/iomap/ |
| D | design.rst | 1 .. SPDX-License-Identifier: GPL-2.0
31 The iteration can involve mappings of file's logical offset ranges to
78 1. Obtain a space mapping via ``->iomap_begin``
80 2. For each sub-unit of work...
89 4. Release the mapping via ``->iomap_end``, if necessary
105 -----------
120 Processes wishing to insert folios must hold this lock in shared
122 Processes wishing to remove folios must hold this lock in exclusive
126 * ``dax_read_lock``: The RCU read lock that dax takes to prevent a
127 device pre-shutdown hook from returning before other threads have
[all …]
|
| D | operations.rst | 1 .. SPDX-License-Identifier: GPL-2.0
35 linked lists of buffer heads instead of the per-folio bitmaps that iomap
42 -----------------------------------
61 --------------------------
63 The ``->iomap_begin`` function for pagecache operations may set the
67 .. code-block:: c
79 - ``get_folio``: Called to allocate and return an active reference to
83 This could be used to `set up per-folio filesystem state
84 <https://lore.kernel.org/all/20190429220934.10415-5-agruenba@redhat.com/>`_
87 - ``put_folio``: Called to unlock and put a folio after a pagecache
[all …]
|
| /Documentation/kernel-hacking/ |
| D | false-sharing.rst | 1 .. SPDX-License-Identifier: GPL-2.0
22 +-----------+ +-----------+
24 +-----------+ +-----------+
28 +----------------------+ +----------------------+
30 +----------------------+ +----------------------+
32 ---------------------------+------------------+-----------------------------
34 +----------------------+
36 +----------------------+
38 +----------------------+
47 There are many real-world cases of performance regressions caused by
[all …]
|
| /Documentation/admin-guide/gpio/ |
| D | gpio-aggregator.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
11 -----------------------------
15 system permissions, on an all-or-nothing basis: either a GPIO controller is
26 write-only attribute files in sysfs.
28 /sys/bus/platform/drivers/gpio-aggregator/
35 .. code-block:: none
48 is a comma-separated list of GPIO offsets and/or
49 GPIO offset ranges denoted by dashes.
52 line 19 of "e6052000.gpio" and GPIO lines 20-21 of
55 .. code-block:: sh
[all …]
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | partition.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 relative offset and size specified. Depending on partition function extra
16 Everything after 'partition-' will be used as the partition name to compare
26 - Rafał Miłecki <rafal@milecki.pl>
30 description: partition's offset and size within the flash
37 read-only:
39 should only be mounted read-only. This is usually used for flash
40 partitions containing early-boot firmware images or data which should
[all …]
|
| /Documentation/filesystems/xfs/ |
| D | xfs-delayed-logging-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0
33 details logged are made up of the changes to in-core structures rather than
34 on-disk structures. Other objects - typically buffers - have their physical
64 place. This means that permanent transactions can be used for one-shot
65 modifications, but one-shot reservations cannot be used for permanent
68 In the code, a one-shot transaction pattern looks somewhat like this::
71 <lock items>
97 While this might look similar to a one-shot transaction, there is an important
123 the on-disk journal.
165 transaction, we have to reserve enough space to record a full leaf-to-root split
[all …]
|
| D | xfs-online-fsck-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Heading 3 uses "----"
25 - To help kernel distributors understand exactly what the XFS online fsck
28 - To help people reading the code to familiarize themselves with the relevant
31 - To help developers maintaining the system by capturing the reasons
59 - Provide a hierarchy of names through which application programs can associate
62 - Virtualize physical storage media across those names, and
64 - Retrieve the named data blobs at any time.
66 - Examine resource usage.
79 cross-references different types of metadata records with each other to look
[all …]
|
| /Documentation/virt/kvm/ |
| D | locking.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 KVM Lock Overview
8 ---------------------
12 - cpus_read_lock() is taken outside kvm_lock
14 - kvm_usage_lock is taken outside cpus_read_lock()
16 - kvm->lock is taken outside vcpu->mutex
18 - kvm->lock is taken outside kvm->slots_lock and kvm->irq_lock
20 - kvm->slots_lock is taken outside kvm->irq_lock, though acquiring
23 - kvm->mn_active_invalidate_count ensures that pairs of
25 use the same memslots array. kvm->slots_lock and kvm->slots_arch_lock
[all …]
|
| /Documentation/arch/arm/ |
| D | vlocks.rst | 2 vlocks for Bare-Metal Mutual Exclusion
5 Voting Locks, or "vlocks" provide a simple low-level mutual exclusion
10 which are otherwise non-coherent, in situations where the hardware
28 ---------
30 The easiest way to explain the vlocks algorithm is with some pseudo-code::
34 int last_vote = -1; /* no votes yet */
40 if (last_vote != -1) {
64 last_vote = -1;
74 priority rule to act as a tie-breaker, or any counters which could
83 ------------------------
[all …]
|
| /Documentation/process/ |
| D | maintainer-tip.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 ---------------------
11 aggregation tree for several sub-maintainer trees. The tip tree gitweb URL
16 - **x86 architecture**
22 x86-specific KVM and XEN patches.
30 mail alias which distributes mails to the x86 top-level maintainer
32 ``linux-kernel@vger.kernel.org``, otherwise your mail ends up only in
35 - **Scheduler**
37 Scheduler development takes place in the -tip tree, in the
38 sched/core branch - with occasional sub-topic trees for
[all …]
|
| /Documentation/power/ |
| D | userland-swsusp.rst | 83 will contain the swap page offset if the call is successful)
90 set the resume partition and the offset (in <PAGE_SIZE>
94 containing the resume device specification and the offset); for swap
95 partitions the offset is always 0, but it is different from zero for
96 swap files (see Documentation/power/swsusp-and-swap-files.rst for
109 immediately enter the suspend-to-RAM state, so this call must always
112 is needed to implement the suspend-to-both mechanism in which the
121 - you cannot read() more than one virtual memory page at a time
122 - read()s across page boundaries are impossible (ie. if you read() 1/2 of
156 SNAPSHOT_ATOMIC_RESTORE will not succeed. Still, this is not a fool-proof
[all …]
|
| /Documentation/driver-api/usb/ |
| D | URB.rst | 1 .. _usb-urb:
6 :Revised: 2000-Dec-05
7 :Again: 2002-Jul-06
8 :Again: 2005-Sep-19
9 :Again: 2017-Mar-29
14 The USB subsystem now has a substantial section at :ref:`usb-hostside-api`
26 - An URB consists of all relevant information to execute any USB transaction
29 - Execution of an URB is inherently an asynchronous operation, i.e. the
33 - Transfers for one URB can be canceled with :c:func:`usb_unlink_urb`
36 - Each URB has a completion handler, which is called after the action
[all …]
|
| /Documentation/filesystems/ |
| D | seq_file.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 https://lwn.net/Articles/driver-porting/
16 Virtual files can provide human-readable output that is easy to get at
23 string. But life gets trickier if the output is long - anything greater
26 position within the virtual file - that position is, likely as not, in the
68 - entry = create_proc_entry("sequence", 0, NULL);
69 - if (entry)
70 - entry->proc_fops = &ct_file_ops;
79 is able to move to a specific position - like the file they implement,
81 in whatever way is convenient - the iterator need only exist
[all …]
|
| D | vfs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - Copyright (C) 1999 Richard Gooch
10 - Copyright (C) 2005 Pekka Enberg
27 ------------------------------
32 cache or dcache). This provides a very fast look-up mechanism to
44 ----------------
64 ---------------
67 structure (this is the kernel-side implementation of file descriptors).
88 .. code-block:: c
99 ->mount() will be attached to the mountpoint, so that when pathname
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | fsl,fman.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Frank Li <Frank.Li@nxp.com>
13 Due to the fact that the FMan is an aggregation of sub-engines (ports, MACs,
19 - fsl,fman
22 FMan block. The offset is 0xc4 from the beginning of the
26 cell-index:
31 The cell-index value may be used by the SoC, to identify the
33 there's a description of the cell-index use in each SoC:
[all …]
|
| /Documentation/fb/ |
| D | intel810.rst | 20 - Intel 810
21 - Intel 810E
22 - Intel 810-DC100
23 - Intel 815 Internal graphics only, 100Mhz FSB
24 - Intel 815 Internal graphics only
25 - Intel 815 Internal graphics and AGP
30 - Choice of using Discrete Video Timings, VESA Generalized Timing
33 - Supports a variable range of horizontal and vertical resolution and
37 - Supports color depths of 8, 16, 24 and 32 bits per pixel
39 - Supports pseudocolor, directcolor, or truecolor visuals
[all …]
|
123