Searched full:pointers (Results 1 – 25 of 181) sorted by relevance
12345678
| /Documentation/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 of valid tagged pointers in this context is always allowed.
84 - The syscall behaviour is undefined for invalid tagged pointers: it may
92 A definition of the meaning of tagged pointers on AArch64 can be found
93 in Documentation/arm64/tagged-pointers.rst.
101 - ``prctl()`` other than pointers to user data either passed directly or
104 - ``ioctl()`` other than pointers to user data either passed directly or
109 Any attempt to use non-zero tagged pointers may result in an error code
|
| D | pointer-authentication.rst | 21 whether pointers have been modified unexpectedly. A PAC is derived from
78 exposed for data pointers and instruction pointers, as the set of PAC
81 pointers).
|
| D | index.rst | 20 tagged-pointers
|
| D | tagged-pointers.rst | 29 - pointer arguments to system calls, including pointers in structures
73 Special care should be taken when using tagged pointers, since it is
|
| /Documentation/filesystems/ |
| D | sysv-fs.txt | 83 of limited size, and every now and then a free block contains pointers
85 contains pointers and so on. The list terminates with a "block number"
161 1 indirect block (pointers to blocks)
162 1 double-indirect block (pointer to pointers to blocks)
165 1 indirect block (pointers to blocks)
166 1 double-indirect block (pointer to pointers to blocks)
167 1 triple-indirect block (pointer to pointers to pointers to blocks)
|
| D | qnx6.txt | 54 addressing block holds up to blocksize / 4 bytes pointers to data blocks.
58 Unused block pointers are always set to ~0 - regardless of root node,
77 The inode structure contains pointers to the filesystem blocks which contain
85 There are also pointers to the first 16 blocks, if the object data can be
107 starting with the superblock longfilename root node pointers.
117 no block pointers and the directory file record pointing to the target file
|
| D | sysfs-tagging.txt | 15 By using the network namespace pointers as tags to separate out the
34 kernfs_node->ns pointers pointing to it.
|
| D | omfs.txt | 80 Lookup requires hashing the filename, then seeking across i_sibling pointers
82 pointers with all-1s (~0).
|
| D | ext2.txt | 141 structure contains pointers to the filesystem blocks which contain the
159 There are pointers to the first 12 blocks which contain the file's data
161 pointers to the next set of blocks), a pointer to a doubly-indirect
162 block (which contains pointers to indirect blocks) and a pointer to a
163 trebly-indirect block (which contains pointers to doubly-indirect blocks).
200 which would normally be used to store the pointers to data blocks.
|
| /Documentation/RCU/ |
| D | rcu_dereference.txt | 37 -not- work in general for char* pointers.
39 o XOR bits to translate pointers, as is done in some
47 "(x-(uintptr_t)x)" for char* pointers. The compiler is within its
84 o Be very careful about comparing pointers obtained from
86 explained, if the two pointers are equal, the compiler could
112 it is safe to compare pointers from rcu_dereference()
113 against NULL pointers.
152 rcu_dereference(). In this case, both pointers depend
168 o The pointers are not equal -and- the compiler does
412 SPARSE CHECKING OF RCU-PROTECTED POINTERS
[all …]
|
| /Documentation/core-api/ |
| 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 | printk-formats.rst | 59 pointers of different types.
69 Plain Pointers
76 Pointers printed without a specifier extension (i.e unadorned %p) are
82 Symbols/Function Pointers
102 parisc64 function pointers are indirect and, in fact, are function
113 Kernel Pointers
120 For printing kernel pointers which should be hidden from unprivileged
131 For printing pointers when you *really* want to print the address. Please
133 kernel memory layout before printing pointers with %px. %px is functionally
136 printing pointers we will be better equipped to find the call sites.
[all …]
|
| D | xarray.rst | 13 of pointers. It meets many of the same needs as a hash or a conventional
32 Normal pointers may be stored in the XArray directly. They must be 4-byte
34 alloc_page(). It isn't true for arbitrary user-space pointers,
35 nor for function pointers. You can store pointers to statically allocated
44 Some users want to store tagged pointers instead of using the marks
48 the tag of an entry. Tagged pointers use the same bits that are used
49 to distinguish value entries from normal pointers, so each user must
50 decide whether they want to store value entries or tagged pointers in
53 The XArray does not support storing IS_ERR() pointers as some
123 xa_destroy(). If the XArray entries are pointers, you may wish
|
| /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/arm64/ |
| D | tagged-pointers.txt | 1 Chinese translated version of Documentation/arm64/tagged-pointers.rst
12 Documentation/arm64/tagged-pointers.rst 的中文翻译
|
| /Documentation/networking/device_drivers/toshiba/ |
| D | spider_net.txt | 19 together with three pointers into the ring that are used to manage its
40 This filling and emptying is managed by three pointers, the "head"
41 and "tail" pointers, managed by the OS, and a hardware current
72 Thus, in an idle system, the GDACTDPA, tail and head pointers will
77 GDACTDPA, tail and head pointers. It will also summarize the contents
154 Both the tail and head pointers are pointing at descr 255, which is
|
| /Documentation/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/media/uapi/v4l/ |
| D | userp.rst | 13 Streaming I/O (User Pointers)
26 can reside for example in virtual or shared memory. Only pointers to
27 data are exchanged, these pointers and meta-information are passed in
36 Example: Initiating streaming I/O with user pointers
|
| /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/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/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/dev-tools/ |
| D | kmemleak.rst | 86 friends are traced and the pointers, together with additional
88 The corresponding freeing function calls are tracked and the pointers
112 Some allocated memory blocks have pointers stored in the kernel's
194 the memory block is known not to contain other pointers and it will no
198 systems, because of pointers temporarily stored in CPU registers or
|
| /Documentation/arm/omap/ |
| D | omap_pm.rst | 72 exposed to drivers through function pointers in driver .platform_data
73 structures. The function pointers are initialized by the `board-*.c`
78 not support these functions should leave these function pointers set
|
| /Documentation/virt/ |
| D | paravirt_ops.rst | 15 pv_ops provides a set of function pointers which represent operations
|
| /Documentation/devicetree/bindings/misc/ |
| D | intel,ixp4xx-ahb-queue-manager.yaml | 15 an 8KB embedded SRAM along with hardware pointers. It is used by both
|
12345678