Searched full:pointer (Results 1 – 25 of 581) sorted by relevance
12345678910>>...24
| /Documentation/arch/arm64/ |
| D | pointer-authentication.rst | 2 Pointer authentication in AArch64 Linux
9 This document briefly describes the provision of pointer authentication
16 The ARMv8.3 Pointer Authentication extension adds primitives that can be
20 The extension uses a Pointer Authentication Code (PAC) to determine
22 a pointer, another value (such as the stack pointer), and a secret key
25 The extension adds instructions to insert a valid PAC into a pointer,
26 and to verify/remove the PAC from a pointer. The PAC occupies a number
27 of high-order bits of the pointer, which varies dependent on the
28 configured virtual address size and whether pointer tagging is in use.
52 The number of bits that the PAC occupies in a pointer is 55 minus the
[all …]
|
| D | tagged-address-abi.rst | 26 this document, a "valid tagged pointer" is a pointer with a potentially
99 valid tagged pointer.
105 - The syscall behaviour for a valid tagged pointer is the same as for
106 the corresponding untagged pointer.
173 strcpy(ptr, "tagged pointer\n");
175 /* syscall with a tagged pointer */
|
| /Documentation/mm/ |
| D | split_page_table_lock.rst | 17 maps PTE and takes PTE table lock, returns pointer to PTE with
18 pointer to its PTE table lock, or returns NULL if no PTE table;
20 maps PTE, returns pointer to PTE with pointer to its PTE table
23 maps PTE, returns pointer to PTE with pointer to its PTE table
27 maps PTE, returns pointer to PTE, or returns NULL if no PTE table;
33 allocates PTE table if needed and takes its lock, returns pointer to
34 PTE with pointer to its lock, or returns NULL if allocation failed;
36 takes PMD table lock, returns pointer to taken lock;
38 returns pointer to PMD table lock;
59 returns pointer to table lock;
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-ext-ctrls.rst | 37 Pointer to struct :c:type:`v4l2_ext_controls`.
61 relevant for pointer-type controls like strings), then the driver will
142 * - :cspan:`2` The ``size`` field is normally 0, but for pointer
174 - A pointer to a string. Valid if this control is of type
178 - A pointer to a matrix control of unsigned 8-bit values. Valid if
182 - A pointer to a matrix control of unsigned 16-bit values. Valid if
186 - A pointer to a matrix control of unsigned 32-bit values. Valid if
190 - A pointer to a matrix control of signed 32-bit values. Valid if
195 - A pointer to a matrix control of signed 64-bit values. Valid if
200 - A pointer to a struct :c:type:`v4l2_area`. Valid if this control is
[all …]
|
| /Documentation/RCU/ |
| D | rcu_dereference.rst | 10 macro's load of the pointer to the later use of that pointer to compute
28 to load an RCU-protected pointer, otherwise CONFIG_PROVE_RCU
33 different values for a single pointer! Without rcu_dereference(),
34 DEC Alpha can load a pointer, dereference that pointer, and
36 of the pointer. (As noted later, in recent kernels READ_ONCE()
40 compiler from deducing the resulting pointer value. Please see
43 value of the pointer, and thus cause misordering.
51 - You are only permitted to use rcu_dereference() on pointer values.
55 cast the pointer to uintptr_t in order to:
58 bits of that pointer. This clearly means that the pointer
[all …]
|
| D | NMI-RCU.rst | 27 This nmi_callback variable is a global function pointer to the current
48 function pointer. If this handler returns zero, do_nmi() invokes the
59 …eference_sched() be necessary on Alpha, given that the code referenced by the pointer is read-only?
107 …eference_sched() be necessary on Alpha, given that the code referenced by the pointer is read-only?
113 just after the new handler was set might see the pointer
118 a compiler with aggressive pointer-value speculation
122 clear to someone reading the code that the pointer is
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 25 describe the received data. This includes a pointer to a buffer
44 descriptor pointer (GDACTDPA). The GDACTDPA points at the descr
52 The tail pointer tails or trails the hardware pointer. When the
53 hardware is ahead, the tail pointer will be pointing at a "full"
55 and advance the tail pointer. Thus, when there is flowing RX traffic,
56 all of the descrs in front of the tail pointer should be "full", and
58 flowing, then the tail pointer can catch up to the hardware pointer.
62 The head pointer (somewhat mis-named) follows after the tail pointer.
63 When traffic is flowing, then the head pointer will be pointing at
68 is flowing RX traffic, everything in front of the head pointer should
[all …]
|
| /Documentation/driver-api/driver-model/ |
| D | design-patterns.rst | 46 pass around a pointer to struct foo like this::
62 This way you always get a pointer back to the correct instance of foo in
103 return a single argument which is a pointer to a struct member in the
108 What container_of() does is to obtain a pointer to the containing struct from
109 a pointer to a member by a simple subtraction using the offsetof() macro from
111 Notice that the contained member must not be a pointer, but an actual member
116 work function to a single pointer.
|
| /Documentation/arch/s390/ |
| D | vfio-ap-locking.rst | 50 The KVM pointer is stored in the in the matrix_mdev instance
71 1. To control access to the KVM pointer (matrix_mdev->kvm) while the vfio_ap
84 found. The KVM pointer (matrix_mdev->kvm) can then be used to determine if
88 It is not necessary to take the Guests Lock to access the KVM pointer if the
89 pointer is not used to plug/unplug devices passed through to the KVM guest;
91 held in order to access the KVM pointer since it is set and cleared under the
94 needs to access the KVM pointer only for the purposes of setting or clearing IRQ
112 pointer of the handler ``(*kvm->arch.crypto.pqap_hook)`` to invoke when the
|
| /Documentation/devicetree/bindings/dma/stm32/ |
| D | st,stm32-mdma.yaml | 23 0x0: Source address pointer is fixed
24 0x2: Source address pointer is incremented after each data transfer
25 0x3: Source address pointer is decremented after each data transfer
27 0x0: Destination address pointer is fixed
28 0x2: Destination address pointer is incremented after each data transfer
29 0x3: Destination address pointer is decremented after each data transfer
|
| /Documentation/filesystems/ |
| D | files.rst | 29 files_struct contains a pointer to struct fdtable through
55 The fdtable pointer must be read within the read-side
88 6. While updating, the fdtable pointer must be looked up while
91 fdtable and making the earlier fdtable pointer stale.
106 the fdtable pointer (fdt) must be loaded after locate_fd().
114 this is reason it is necessary to verify that the pointer is the same
120 that was always very dodgy and it was only usable for non-pointer data
|
| /Documentation/hwmon/ |
| D | hwmon-kernel-api.rst | 60 The parameter of this function is the pointer to the registered hardware
88 `struct device *dev` Pointer to parent device
91 `const struct hwmon_chip_info *info` Pointer to chip description.
96 This function returns a pointer to the created hardware monitoring device
109 Pointer to device operations.
127 Pointer to a function to return the file mode for each supported
131 Pointer to a function for reading a value from the chip. This function
135 Pointer to a function for writing a value to the chip. This function is
167 Pointer to a 0-terminated list of configuration values for each
256 Pointer to device private data structure.
[all …]
|
| /Documentation/mhi/ |
| D | mhi.rst | 95 [Read Pointer (RP)] ----------->[Ring Element] } TD
96 [Write Pointer (WP)]- [Ring Element]
104 * Host sets the base pointer, read pointer, and write pointer in corresponding
122 [Read Pointer (RP)] ----------->[Ring Element] } ED
123 [Write Pointer (WP)]- [Ring Element]
131 * Host sets the base pointer, read pointer, and write pointer in corresponding
145 single buffer pointer, the size of the buffer, and additional control
|
| /Documentation/bpf/ |
| D | map_sk_storage.rst | 42 it will be zero initialized. Returns a pointer to the storage on success, or
46 - ``sk`` is a kernel ``struct sock`` pointer for LSM or tracing programs.
47 - ``sk`` is a ``struct bpf_sock`` pointer for other program types.
72 identified by a `socket` ``fd`` stored in the pointer ``key``. The pointer
96 the socket identified by a `socket` ``fd`` stored in the pointer
108 socket identified by a `socket` ``fd`` stored in the pointer ``key``. Returns
|
| D | kfuncs.rst | 74 of the pointer is used. Without __sz annotation, a kfunc cannot accept a void
75 pointer.
93 ID in program's BTF and return a sized pointer to it. Each type ID will have a
135 annotation, the verifier will reject the program if a null pointer is passed in with
205 The KF_ACQUIRE flag is used to indicate that the kfunc returns a pointer to a
206 refcounted object. The verifier will then ensure that the pointer to the object
215 The KF_RET_NULL flag is used to indicate that the pointer returned by the kfunc
216 may be NULL. Hence, it forces the user to do a NULL check on the pointer
224 The KF_RELEASE flag is used to indicate that the kfunc releases the pointer
225 passed in to it. There can be only one referenced pointer that can be passed
[all …]
|
| D | verifier.rst | 16 At the start of the program the register R1 contains a pointer to context
21 since addition of two valid pointers makes invalid pointer.
22 (In 'secure' mode verifier will reject any type of pointer arithmetic to make
56 will be rejected, since R1 doesn't have a valid pointer type at the time of
59 At the start R1 type is PTR_TO_CTX (a pointer to generic ``struct bpf_context``)
88 Pointer register spill/fill is tracked as well, since four (R6-R9)
116 bpf_verifier.h, which unifies tracking of scalar and pointer values. Each
118 written to), SCALAR_VALUE (some value which is not usable as a pointer), or a
119 pointer type. The types of pointers describe their base, as follows:
123 Pointer to bpf_context.
[all …]
|
| /Documentation/core-api/ |
| D | kref.rst | 56 1) If you make a non-temporary copy of a pointer, especially if
62 If you already have a valid pointer to a kref-ed structure (the
65 2) When you are done with a pointer, you must call kref_put()::
69 If this is the last reference to the pointer, the release
71 a valid pointer to a kref-ed structure without already
72 holding a valid pointer, it is safe to do this without
76 without already holding a valid pointer, it must serialize access
127 since we already have a valid pointer that we own a refcount for. The
129 already holding a pointer.
173 holding a valid pointer. You must add a mutex (or some other lock).
[all …]
|
| D | assoc_array.rst | 48 The implementation uses a tree of 16-pointer nodes internally that are indexed
85 The script appears as outside of the API as a pointer of the type::
186 significant bit of the pointer must be zero as it's used to type-mark
357 * A NULL pointer, indicating that the slot is empty.
358 * A pointer to an object (a leaf).
359 * A pointer to a node at the next level.
360 * A pointer to a shortcut.
438 space. The leaves can be in any slot not occupied by a metadata pointer. It
440 metadata pointer. If the metadata pointer is there, any leaf whose key matches
441 the metadata key prefix must be in the subtree that the metadata pointer points
[all …]
|
| /Documentation/filesystems/spufs/ |
| D | spu_run.rst | 28 uled to a physical SPU, it starts execution at the instruction pointer
37 When spu_run returns, the current value of the SPU instruction pointer
41 event can be a NULL pointer or point to an extended status code that
97 EFAULT npc is not a valid pointer or status is neither NULL nor a valid
98 pointer.
|
| /Documentation/admin-guide/device-mapper/ |
| D | kcopyd.rst | 29 pointer, pointers to the source and destination io_regions, the name of a
30 completion callback routine, and a pointer to some context data for the copy::
40 passing back the user's context pointer. It will also indicate if a read or
|
| /Documentation/scsi/ |
| D | scsi_mid_low_api.rst | 108 pointer members not explicitly initialized.
184 (a pointer is returned by scsi_host_alloc()). Such instances are "owned"
224 (a pointer is passed as the parameter to slave_alloc() and
242 returns a pointer to new instance of struct
258 a copy of a pointer to a scsi_device instance it should use scsi_device_get()
259 to bump its reference count. When it is finished with the pointer it can
319 * @shost: pointer to scsi host instance
324 * Returns pointer to new struct scsi_device instance or
325 * ERR_PTR(-ENODEV) (or some other bent pointer) if something is
346 * @shost: pointer to scsi host instance
[all …]
|
| D | hptiop.rst | 68 0x0 Inbound Queue Head Pointer
69 0x4 Inbound Queue Tail Pointer
70 0x8 Outbound Queue Head Pointer
71 0xC Outbound Queue Tail Pointer
91 0x4018 Inbound List Write Pointer
95 0x4058 Outbound List Copy Pointer Shadow Base Address Low
96 0x405C Outbound List Copy Pointer Shadow Base Address High
168 Set up the inbound list write pointer with the index of previous unit,
171 - Post the inbound list writer pointer to IOP.
176 put into the copy pointer shadow register. An outbound interrupt will be
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-msi-laptop | 4 Contact: "Lennart Poettering <mzxreary@0pointer.de>"
11 Contact: "Lennart Poettering <mzxreary@0pointer.de>"
20 Contact: "Lennart Poettering <mzxreary@0pointer.de>"
27 Contact: "Lennart Poettering <mzxreary@0pointer.de>"
|
| /Documentation/sound/cards/ |
| D | hdspm.rst | 70 * Hardware-pointer -- 2 Modi
73 The Card supports the readout of the actual Buffer-pointer,
79 precise-pointer.
83 (Hint: Experimenting I found that the pointer is maximum 64 to
85 safe pointer for writing, which is used on this mode inside
89 * Precise Pointer -- off
90 interrupt used for pointer-calculation
92 * Precise Pointer -- on
93 hardware pointer used.
357 Enable precise pointer, or disable.
|
| /Documentation/driver-api/ |
| D | vme.rst | 11 A pointer to a structure of type :c:type:`struct vme_driver <vme_driver>` must
17 element is a pointer to a string holding the device driver's name.
35 The '.probe' element should contain a pointer to the probe routine. The
36 probe routine is passed a :c:type:`struct vme_dev <vme_dev>` pointer as an
55 driver is called. The probe routine is passed a pointer to the devices
56 device structure. This pointer should be saved, it will be required for
70 that meets the requirements, returning a pointer of type vme_resource that
76 the requirements can not be found a NULL pointer will be returned.
80 and :c:func:`vme_dma_free`) should be passed the pointer to the resource
222 pointer parameter is provided, the value of which is passed to the callback
[all …]
|
12345678910>>...24