| /Linux-v5.4/sound/firewire/dice/ |
| D | dice-transaction.c | 273 __be32 *pointers; in get_subaddrs() local
279 pointers = kmalloc_array(ARRAY_SIZE(min_values), sizeof(__be32), in get_subaddrs()
281 if (pointers == NULL) in get_subaddrs()
290 DICE_PRIVATE_SPACE, pointers, in get_subaddrs()
296 data = be32_to_cpu(pointers[i]); in get_subaddrs()
303 if (be32_to_cpu(pointers[1]) > 0x18) { in get_subaddrs()
310 be32_to_cpu(pointers[0]) * 4 + GLOBAL_VERSION, in get_subaddrs()
328 dice->global_offset = be32_to_cpu(pointers[0]) * 4; in get_subaddrs()
329 dice->tx_offset = be32_to_cpu(pointers[2]) * 4; in get_subaddrs()
330 dice->rx_offset = be32_to_cpu(pointers[4]) * 4; in get_subaddrs()
[all …]
|
| D | dice-extension.c | 142 __be32 *pointers; in snd_dice_detect_extension_formats() local
147 pointers = kmalloc_array(9, sizeof(__be32) * 2, GFP_KERNEL); in snd_dice_detect_extension_formats()
148 if (pointers == NULL) in snd_dice_detect_extension_formats()
152 DICE_EXT_APP_SPACE, pointers, in snd_dice_detect_extension_formats()
162 if (pointers[i * 2] == pointers[j * 2]) in snd_dice_detect_extension_formats()
167 section_addr = DICE_EXT_APP_SPACE + be32_to_cpu(pointers[12]) * 4; in snd_dice_detect_extension_formats()
170 kfree(pointers); in snd_dice_detect_extension_formats()
|
| /Linux-v5.4/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
|
| /Linux-v5.4/fs/btrfs/ |
| D | raid56.c | 1197 void **pointers = rbio->finish_pointers; in finish_rmw() local
1252 pointers[stripe] = kmap(p); in finish_rmw()
1258 pointers[stripe++] = kmap(p); in finish_rmw()
1268 pointers[stripe++] = kmap(p); in finish_rmw()
1271 pointers); in finish_rmw()
1274 copy_page(pointers[nr_data], pointers[0]); in finish_rmw()
1275 run_xor(pointers + 1, nr_data - 1, PAGE_SIZE); in finish_rmw()
1814 void **pointers; in __raid_recover_end_io() local
1820 pointers = kcalloc(rbio->real_stripes, sizeof(void *), GFP_NOFS); in __raid_recover_end_io()
1821 if (!pointers) { in __raid_recover_end_io()
[all …]
|
| /Linux-v5.4/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.
|
| /Linux-v5.4/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-fields.txt | 20 The _tep_event_common_fields()_ function returns an array of pointers to common
24 The _tep_event_fields()_ function returns an array of pointers to event specific
31 an array of pointers to tep_format_field structures in case of success, or
|
| D | libtraceevent-event_list.txt | 27 The _tep_list_events()_ function returns an array of pointers to the events,
46 The _tep_list_events()_ function returns an array of pointers to events.
50 The _tep_list_events_copy()_ function returns an array of pointers to events.
|
| /Linux-v5.4/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 的中文翻译
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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
415 pointers, which can result in "interesting" bugs due to compiler
[all …]
|
| /Linux-v5.4/tools/objtool/Documentation/ |
| D | stack-validation.txt | 35 Frame pointers are used for debugging purposes. They allow runtime
40 For some architectures, frame pointers are enabled by
42 required by the ABI (sometimes referred to as "backchain pointers").
45 frame pointers when the -fno-omit-frame-pointer option is used.
51 For stack traces based on frame pointers to be reliable, all
58 pointers enabled:
95 destroyed. This is an inherent limitation of frame pointers.
99 An alternative to frame pointers and DWARF, ORC unwind data can be
100 used to walk the stack. Unlike frame pointers, ORC data is out of
|
| /Linux-v5.4/drivers/staging/iio/Documentation/ |
| D | ring.txt | 15 which in turn contains the 4 function pointers
22 The function pointers within here are used to allow the core to handle
|
| /Linux-v5.4/Documentation/core-api/ |
| D | assoc_array.rst | 11 1. Objects are opaque pointers. The implementation does not care where they
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
525 leaves in a node before following any of its metadata pointers).
[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
|
| D | printk-formats.rst | 59 pointers of different types.
102 parisc64 function pointers are indirect and, in fact, are function
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.
371 For printing name of block_device pointers.
|
| /Linux-v5.4/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
|
| /Linux-v5.4/drivers/opp/ |
| D | Kconfig | 11 OPP layer organizes the data internally using device pointers
|
| /Linux-v5.4/drivers/media/radio/wl128x/ |
| D | Kconfig | 15 this API and pointers to "v4l2" programs may be found at
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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
|
