Searched full:pointers (Results 1 – 25 of 223) sorted by relevance
123456789
| /Documentation/arch/arm64/ |
| D | tagged-address-abi.rst | 17 userspace (EL0) to perform memory accesses through 64-bit pointers with
19 syscall ABI that allows userspace to pass certain tagged pointers to
48 tagged pointers in this context is allowed with these exceptions:
55 incorrectly accept valid tagged pointers for the ``brk()``,
65 incorrectly accept valid tagged pointers for this system call.
101 - The syscall behaviour is undefined for invalid tagged pointers: it may
109 A definition of the meaning of tagged pointers on AArch64 can be found
110 in Documentation/arch/arm64/tagged-pointers.rst.
118 - ``prctl()`` other than pointers to user data either passed directly or
121 - ``ioctl()`` other than pointers to user data either passed directly or
[all …]
|
| D | pointer-authentication.rst | 21 whether pointers have been modified unexpectedly. A PAC is derived from
77 exposed for data pointers and instruction pointers, as the set of PAC
80 pointers).
128 instructions to sign and authenticate function pointers and other pointers
131 pointers.
|
| D | index.rst | 30 tagged-pointers
|
| D | tagged-pointers.rst | 29 - pointer arguments to system calls, including pointers in structures
86 Special care should be taken when using tagged pointers, since it is
|
| /Documentation/core-api/ |
| D | folio_queue.rst | 36 A pair of pointers are provided, ``next`` and ``prev``, that point to the
39 sibling pointers in terminal segments should be NULL.
43 * an ordered sequence of folio pointers,
67 necessarily initialise all the folio pointers, so care must be taken to check
184 queue. The iov iterator functions will follow the next pointers when advancing
185 and prev pointers when reverting when needed.
206 head and tail pointers from collapsing.
|
| D | printk-formats.rst | 61 pointers of different types.
71 Plain Pointers
78 Pointers printed without a specifier extension (i.e unadorned %p) are
96 Error Pointers
103 For printing error pointers (i.e. a pointer for which IS_ERR() is true)
108 Symbols/Function Pointers
141 Probed Pointers from BPF / tracing
155 Kernel Pointers
162 For printing kernel pointers which should be hidden from unprivileged
168 section about %p above for discussion about how to manage hashing pointers
[all …]
|
| D | assoc_array.rst | 11 1. Objects are opaque pointers. The implementation does not care where they
16 Pointers to objects _must_ be zero in the least significant bit.
52 pack leaf object pointers into spare space in the node rather than making an
187 pointers internally.
340 can contain mixtures of leaves and metadata pointers.
434 pointers - even if some of those leaves would like to be in the same slot.
436 A node can contain a heterogeneous mix of leaves and metadata pointers.
437 Metadata pointers must be in the slots that match their subdivisions of key
477 Each node has a maximum capacity of 16 leaves and metadata pointers. If the
523 new layout until we follow the back pointers - at which point we've
[all …]
|
| D | xarray.rst | 13 of pointers. It meets many of the same needs as a hash or a conventional
28 Normal pointers may be stored in the XArray directly. They must be 4-byte
30 alloc_page(). It isn't true for arbitrary user-space pointers,
31 nor for function pointers. You can store pointers to statically allocated
40 Some users want to tag the pointers they store in the XArray. You can
43 to retrieve the tag of an entry. Tagged pointers use the same bits that
44 are used to distinguish value entries from normal pointers, so you must
45 decide whether they want to store value entries or tagged pointers in
48 The XArray does not support storing IS_ERR() pointers as some
111 xa_destroy(). If the XArray entries are pointers, you may wish
|
| /Documentation/filesystems/ |
| D | sysv-fs.rst | 114 of limited size, and every now and then a free block contains pointers
116 contains pointers and so on. The list terminates with a "block number"
214 - 1 indirect block (pointers to blocks)
215 - 1 double-indirect block (pointer to pointers to blocks)
220 - 1 indirect block (pointers to blocks)
221 - 1 double-indirect block (pointer to pointers to blocks)
222 - 1 triple-indirect block (pointer to pointers to pointers to blocks)
|
| D | qnx6.rst | 61 addressing block holds up to blocksize / 4 bytes pointers to data blocks.
65 Unused block pointers are always set to ~0 - regardless of root node,
86 The inode structure contains pointers to the filesystem blocks which contain
94 There are also pointers to the first 16 blocks, if the object data can be
122 starting with the superblock longfilename root node pointers.
133 no block pointers and the directory file record pointing to the target file
|
| /Documentation/devicetree/ |
| D | overlay-notes.rst | 127 OF_OVERLAY_PRE_REMOVE may store pointers to a device tree node in the overlay
128 or its content but these pointers must not persist past the notifier callback
136 are not allowed to store pointers to a device tree node in the overlay
137 or its content. The overlay code does not protect against such pointers
147 pointers to the overlay nodes or data. Any example of an inadvertent use
148 of such pointers is if a driver or subsystem module is loaded after an
|
| /Documentation/RCU/ |
| D | rcu_dereference.rst | 7 important to correct use of things like RCU. To this end, the pointers
60 *not* work in general for char* pointers.
62 - XOR bits to translate pointers, as is done in some
70 "(x-(uintptr_t)x)" for char* pointers. The compiler is within its
107 - Be very careful about comparing pointers obtained from
109 explained, if the two pointers are equal, the compiler could
135 it is safe to compare pointers from rcu_dereference()
136 against NULL pointers.
181 rcu_dereference(). In this case, both pointers depend
197 - The pointers are not equal *and* the compiler does
[all …]
|
| /Documentation/networking/ |
| D | sysfs-tagging.rst | 18 By using the network namespace pointers as tags to separate out
37 kernfs_node->ns pointers pointing to it.
|
| /Documentation/devicetree/bindings/net/ |
| D | marvell-neta-bm.txt | 12 - pool<0 : 3>,capacity: size of external buffer pointers' ring maintained
18 pointers' pool (id 0 : 3). It will be taken into consideration only when pool
|
| /Documentation/translations/zh_CN/arch/arm64/ |
| D | tagged-pointers.txt | 1 Chinese translated version of Documentation/arch/arm64/tagged-pointers.rst
12 Documentation/arch/arm64/tagged-pointers.rst 的中文翻译
|
| /Documentation/userspace-api/media/v4l/ |
| D | userp.rst | 7 Streaming I/O (User Pointers)
20 can reside for example in virtual or shared memory. Only pointers to
21 data are exchanged, these pointers and meta-information are passed in
30 Example: Initiating streaming I/O with user pointers
|
| /Documentation/translations/zh_TW/arch/arm64/ |
| D | tagged-pointers.txt | 3 Chinese translated version of Documentation/arch/arm64/tagged-pointers.rst
15 Documentation/arch/arm64/tagged-pointers.rst 的中文翻譯
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 21 together with three pointers into the ring that are used to manage its
42 This filling and emptying is managed by three pointers, the "head"
43 and "tail" pointers, managed by the OS, and a hardware current
74 Thus, in an idle system, the GDACTDPA, tail and head pointers will
79 GDACTDPA, tail and head pointers. It will also summarize the contents
156 Both the tail and head pointers are pointing at descr 255, which is
|
| /Documentation/driver-api/ |
| D | ioctl.rst | 33 and use pointers for passing data.
127 for data pointers, with the upper bit being ignored. When running such
141 are pointers to compatible data structures.
154 * Pointers have the same problem, in addition to requiring the
156 in place of pointers, which requires a cast to ``uintptr_t`` in user
216 through normal kernel pointers.
|
| /Documentation/arch/x86/ |
| D | orc-unwinder.rst | 28 ORC vs frame pointers
31 With frame pointers enabled, GCC adds instrumentation code to every
38 frame pointers and enable the ORC unwinder, you get a nice performance
49 Another benefit of ORC compared to frame pointers is that it can
55 The main disadvantage of the ORC unwinder compared to frame pointers is
|
| /Documentation/process/ |
| D | volatile-considered-harmful.rst | 57 directly through pointers is frowned upon and does not work on all
92 - Pointers to data structures in coherent memory which might be modified
94 used by a network adapter, where that adapter changes pointers to
|
| /Documentation/arch/x86/x86_64/ |
| D | 5level-paging.rst | 38 at least some JIT compilers use higher bits in pointers to encode their
39 information. It collides with valid pointers with 5-level paging and
|
| /Documentation/infiniband/ |
| D | user_verbs.rst | 40 between kernel pointers and opaque userspace handles, so that kernel
41 pointers are never exposed to userspace and userspace cannot trick
|
| /Documentation/dev-tools/ |
| D | kmemleak.rst | 85 friends are traced and the pointers, together with additional
87 The corresponding freeing function calls are tracked and the pointers
111 Some allocated memory blocks have pointers stored in the kernel's
192 the memory block is known not to contain other pointers and it will no
196 systems, because of pointers temporarily stored in CPU registers or
|
| /Documentation/userspace-api/ |
| D | futex2.rst | 42 If userspace has 32-bit pointers, it should do a explicit cast to make sure
44 both 32/64-bit pointers.
|
123456789