| /Linux-v5.10/sound/firewire/dice/ | 
| D | dice-transaction.c | 273 	__be32 *pointers;  in get_subaddrs()  local279 	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()  local147 	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()
 170 	section_addr = DICE_EXT_APP_SPACE + be32_to_cpu(pointers[12]) * 4;  in snd_dice_detect_extension_formats()
 173 	kfree(pointers);  in snd_dice_detect_extension_formats()
 
 | 
| /Linux-v5.10/Documentation/arm64/ | 
| D | tagged-address-abi.rst | 17 userspace (EL0) to perform memory accesses through 64-bit pointers with19 syscall ABI that allows userspace to pass certain tagged pointers to
 48    tagged pointers in this context is allowed with the exception of
 54    incorrectly accept valid tagged pointers for the ``brk()``,
 91 - The syscall behaviour is undefined for invalid tagged pointers: it may
 99 A definition of the meaning of tagged pointers on AArch64 can be found
 100 in Documentation/arm64/tagged-pointers.rst.
 108 - ``prctl()`` other than pointers to user data either passed directly or
 111 - ``ioctl()`` other than pointers to user data either passed directly or
 116 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 from78 exposed for data pointers and instruction pointers, as the set of PAC
 81 pointers).
 
 | 
| D | index.rst | 25     tagged-pointers
 | 
| D | tagged-pointers.rst | 29  - pointer arguments to system calls, including pointers in structures73 Special care should be taken when using tagged pointers, since it is
 
 | 
| /Linux-v5.10/fs/btrfs/ | 
| D | raid56.c | 1192 	void **pointers = rbio->finish_pointers;  in finish_rmw()  local1244 			pointers[stripe] = kmap(p);  in finish_rmw()
 1250 		pointers[stripe++] = kmap(p);  in finish_rmw()
 1260 			pointers[stripe++] = kmap(p);  in finish_rmw()
 1263 						pointers);  in finish_rmw()
 1266 			copy_page(pointers[nr_data], pointers[0]);  in finish_rmw()
 1267 			run_xor(pointers + 1, nr_data - 1, PAGE_SIZE);  in finish_rmw()
 1790 	void **pointers;  in __raid_recover_end_io()  local
 1796 	pointers = kcalloc(rbio->real_stripes, sizeof(void *), GFP_NOFS);  in __raid_recover_end_io()
 1797 	if (!pointers) {  in __raid_recover_end_io()
 [all …]
 
 | 
| /Linux-v5.10/Documentation/filesystems/ | 
| D | sysv-fs.rst | 114       of limited size, and every now and then a free block contains pointers116       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
 
 | 
| /Linux-v5.10/tools/lib/traceevent/Documentation/ | 
| D | libtraceevent-fields.txt | 20 The _tep_event_common_fields()_ function returns an array of pointers to common24 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.10/Documentation/translations/zh_CN/arm64/ | 
| D | tagged-pointers.txt | 1 Chinese translated version of Documentation/arm64/tagged-pointers.rst12 Documentation/arm64/tagged-pointers.rst 的中文翻译
 
 | 
| /Linux-v5.10/Documentation/devicetree/bindings/net/ | 
| D | marvell-neta-bm.txt | 12 - pool<0 : 3>,capacity: size of external buffer pointers' ring maintained18   pointers' pool (id 0 : 3). It will be taken into consideration only when pool
 
 | 
| /Linux-v5.10/Documentation/RCU/ | 
| D | rcu_dereference.rst | 40 		-not- work in general for char* pointers.42 	-	XOR bits to translate pointers, as is done in some
 50 	"(x-(uintptr_t)x)" for char* pointers.	The compiler is within its
 87 -	Be very careful about comparing pointers obtained from
 89 	explained, if the two pointers are equal, the compiler could
 115 		it is safe to compare pointers from rcu_dereference()
 116 		against NULL pointers.
 155 		rcu_dereference().  In this case, both pointers depend
 171 	-	The pointers are not equal -and- the compiler does
 422 pointers, which can result in "interesting" bugs due to compiler
 [all …]
 
 | 
| /Linux-v5.10/Documentation/networking/ | 
| D | sysfs-tagging.rst | 18 By using the network namespace pointers as tags to separate out37 kernfs_node->ns pointers pointing to it.
 
 | 
| /Linux-v5.10/tools/objtool/Documentation/ | 
| D | stack-validation.txt | 35    Frame pointers are used for debugging purposes.  They allow runtime40    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.10/Documentation/core-api/ | 
| D | assoc_array.rst | 11 1. Objects are opaque pointers.  The implementation does not care where they52 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 | printk-formats.rst | 61 pointers of different types.91 For printing error pointers (i.e. a pointer for which IS_ERR() is true)
 138 For printing kernel pointers which should be hidden from unprivileged
 149 For printing pointers when you *really* want to print the address. Please
 151 kernel memory layout before printing pointers with %px. %px is functionally
 154 printing pointers we will be better equipped to find the call sites.
 168 	printk("test: difference between pointers: %td\n", ptr2 - ptr1);
 403 For printing name of block_device pointers.
 
 | 
| D | xarray.rst | 13 of pointers.  It meets many of the same needs as a hash or a conventional28 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
 
 | 
| /Linux-v5.10/Documentation/x86/x86_64/ | 
| D | 5level-paging.rst | 38 at least some JIT compilers use higher bits in pointers to encode their39 information. It collides with valid pointers with 5-level paging and
 
 | 
| /Linux-v5.10/drivers/media/radio/wl128x/ | 
| D | Kconfig | 14 	  this API and pointers to "v4l2" programs may be found at
 | 
| /Linux-v5.10/drivers/opp/ | 
| D | Kconfig | 11 	  OPP layer organizes the data internally using device pointers
 | 
| /Linux-v5.10/Documentation/x86/ | 
| D | orc-unwinder.rst | 28 ORC vs frame pointers31 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.10/Documentation/networking/device_drivers/ethernet/toshiba/ | 
| D | spider_net.rst | 21 together with three pointers into the ring that are used to manage its42 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
 
 | 
| /Linux-v5.10/Documentation/infiniband/ | 
| D | user_verbs.rst | 40   between kernel pointers and opaque userspace handles, so that kernel41   pointers are never exposed to userspace and userspace cannot trick
 
 |