| /linux-6.12.1/arch/powerpc/platforms/cell/ |
| D | spu_syscalls.c | 26 struct spufs_calls *calls = NULL; in spufs_calls_get() local
29 calls = rcu_dereference(spufs_calls); in spufs_calls_get()
30 if (calls && !try_module_get(calls->owner)) in spufs_calls_get()
31 calls = NULL; in spufs_calls_get()
34 return calls; in spufs_calls_get()
37 static inline void spufs_calls_put(struct spufs_calls *calls) in spufs_calls_put() argument
39 BUG_ON(calls != spufs_calls); in spufs_calls_put()
52 static inline void spufs_calls_put(struct spufs_calls *calls) { } in spufs_calls_put() argument
60 struct spufs_calls *calls; in SYSCALL_DEFINE4() local
62 calls = spufs_calls_get(); in SYSCALL_DEFINE4()
[all …]
|
| /linux-6.12.1/drivers/misc/cxl/ |
| D | base.c | 24 struct cxl_calls *calls = NULL; in cxl_calls_get() local
27 calls = rcu_dereference(cxl_calls); in cxl_calls_get()
28 if (calls && !try_module_get(calls->owner)) in cxl_calls_get()
29 calls = NULL; in cxl_calls_get()
32 return calls; in cxl_calls_get()
35 static inline void cxl_calls_put(struct cxl_calls *calls) in cxl_calls_put() argument
37 BUG_ON(calls != cxl_calls); in cxl_calls_put()
50 static inline void cxl_calls_put(struct cxl_calls *calls) { } in cxl_calls_put() argument
69 struct cxl_calls *calls; in cxl_slbia() local
71 calls = cxl_calls_get(); in cxl_slbia()
[all …]
|
| /linux-6.12.1/Documentation/arch/powerpc/ |
| D | eeh-pci-error-recovery.rst | 177 It saves the device BAR's and then calls rpaphp_unconfig_pci_adapter().
184 any bridges underneath. It then calls rpaphp_enable_pci_slot(),
201 calls
204 calls
207 calls
210 calls
213 calls
216 calls
219 calls
223 calls
[all …]
|
| /linux-6.12.1/tools/testing/selftests/bpf/verifier/ |
| D | calls.c | 2 "calls: invalid kfunc call not eliminated",
13 "calls: invalid kfunc call unreachable",
25 "calls: invalid kfunc call: ptr_to_mem to struct with non-scalar",
40 "calls: invalid kfunc call: ptr_to_mem to struct with nesting depth > 4",
55 "calls: invalid kfunc call: ptr_to_mem to struct with FAM",
70 "calls: invalid kfunc call: reg->type != PTR_TO_CTX",
85 "calls: invalid kfunc call: void * not allowed in func proto without mem size arg",
100 "calls: trigger reg2btf_ids[reg->type] for reg->type > __BPF_REG_TYPE_MAX",
119 "calls: invalid kfunc call: reg->off must be zero when passed to release kfunc",
142 "calls: invalid kfunc call: don't match first member type when passed to release kfunc",
[all …]
|
| /linux-6.12.1/include/uapi/linux/ |
| D | sockios.h | 7 * Definitions of the socket-level I/O control calls.
51 /* Routing table calls. */
113 /* ARP cache control calls. */
114 /* 0x8950 - 0x8952 * obsolete calls, don't re-use */
119 /* RARP cache control calls. */
124 /* Driver configuration calls */
129 /* DLCI configuration calls */
137 /* bonding calls */
146 /* bridge calls */
156 /* Device private ioctl calls */
[all …]
|
| /linux-6.12.1/Documentation/i2c/ |
| D | dev-interface.rst | 93 the means of read() and write() calls. In particular, so-called combined
147 You can do plain I2C transactions by using read(2) and write(2) calls.
185 1) Your program opens /dev/i2c-N and calls ioctl() on it, as described in
188 2) These open() and ioctl() calls are handled by the i2c-dev kernel
193 3) Some ioctl() calls are for administrative tasks and are handled by
198 4) Other ioctl() calls are converted to in-kernel function calls by
205 difference between these calls that came from user-space through i2c-dev
206 and calls that would have been performed by kernel I2C chip drivers
212 implementing these standard calls. i2c.h:i2c_get_functionality() calls
214 i2c-core-smbus.c:i2c_smbus_xfer() calls either
[all …]
|
| /linux-6.12.1/Documentation/mm/ |
| D | page_frags.rst | 18 and tracks allows multiple calls to make use of a cached page. The
19 advantage to doing this is that multiple calls to get_page can be avoided
21 this caching it is required that any calls to the cache be protected by
27 netdev_alloc_frag and __netdev_alloc_skb calls. The napi_alloc_cache is
28 used by callers of the __napi_alloc_frag and napi_alloc_skb calls. The
29 main difference between these two calls is the context in which they may be
|
| /linux-6.12.1/Documentation/process/ |
| D | adding-syscalls.rst | 16 the alternatives might be suitable instead. Although system calls are the
63 together with the corresponding follow-up system calls --
68 For simpler system calls that only take a couple of arguments, the preferred
79 For more sophisticated system calls that involve a larger number of arguments,
125 what it means to use the :manpage:`poll(2)` family of system calls on that file
146 (For more details on the rationale of the \*at() calls, see the
179 To make new system calls easy to review, it's best to divide up the patchset
209 calls are invoked::
222 note that if multiple new system calls are added in the same merge window,
269 Compatibility System Calls (Generic)
[all …]
|
| /linux-6.12.1/arch/hexagon/ |
| D | Makefile | 13 # We must use long-calls:
14 KBUILD_CFLAGS += -mlong-calls
16 # Modules must use either long-calls, or use pic/plt.
17 # Use long-calls for now, it's easier. And faster.
20 KBUILD_CFLAGS_MODULE += -mlong-calls
|
| /linux-6.12.1/tools/perf/scripts/python/bin/ |
| D | export-to-sqlite-report | 3 # args: [database name] [columns] [calls]
13 echo "usage: export-to-sqlite-report [database name] [columns] [calls]"
19 calls=$3
29 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/export-to-sqlite.py $dbname $columns $calls
|
| D | export-to-postgresql-report | 3 # args: [database name] [columns] [calls]
13 echo "usage: export-to-postgresql-report [database name] [columns] [calls]"
19 calls=$3
29 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/export-to-postgresql.py $dbname $columns $calls
|
| /linux-6.12.1/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | pipeline.json | 8 …ict the following branch types: conditional branches, direct calls and jumps, indirect calls and j…
17 …ict the following branch types: conditional branches, direct calls and jumps, indirect calls and j…
27 …ict the following branch types: conditional branches, direct calls and jumps, indirect calls and j…
37 …ict the following branch types: conditional branches, direct calls and jumps, indirect calls and j…
47 …ict the following branch types: conditional branches, direct calls and jumps, indirect calls and j…
57 …ict the following branch types: conditional branches, direct calls and jumps, indirect calls and j…
67 …ict the following branch types: conditional branches, direct calls and jumps, indirect calls and j…
77 …ict the following branch types: conditional branches, direct calls and jumps, indirect calls and j…
87 …ict the following branch types: conditional branches, direct calls and jumps, indirect calls and j…
97 …ict the following branch types: conditional branches, direct calls and jumps, indirect calls and j…
|
| /linux-6.12.1/Documentation/infiniband/ |
| D | core_locking.rst | 54 if multiple function calls using the same object are run
57 The IB midlayer does not perform any serialization of function calls.
64 information between different calls of ib_poll_cq() is not defined.
102 consumers when it calls ib_register_device(), all initialization
108 semaphores that could cause deadlock if a consumer calls back into
109 the driver across these calls.
|
| /linux-6.12.1/Documentation/crypto/ |
| D | intro.rst | 32 however, does not discuss all API calls available to data transformation
57 following phases that are reflected in the API calls applicable to such
67 When using the initialization API calls, a cipher handle is created and
69 API calls that refer to the data structure type a consumer is expected
70 to receive and subsequently to use. The initialization API calls have
|
| /linux-6.12.1/Documentation/core-api/ |
| D | debug-objects.rst | 29 object type and add calls into the debug code at appropriate places. The
37 The debug calls provided by debugobjects are:
76 it calls the fixup_init function of the object type description
99 it calls the fixup_init function of the object type description
123 it calls the fixup_activate function of the object type description
131 objects. The fixup function checks whether the object is valid and calls
162 destroyed objects. When debugobjects detects an error, then it calls the
178 debugobjects detects an error, then it calls the fixup_free function of
193 When the real object is not tracked by debugobjects, it calls
252 case it is it calls debug_object_init() and debug_object_activate()
|
| /linux-6.12.1/Documentation/bpf/standardization/ |
| D | abi.rst | 19 * R0: return value from function calls, and exit value for BPF programs
20 * R1 - R5: arguments for function calls
21 * R6 - R9: callee saved registers that function calls will preserve
25 necessary across calls.
|
| /linux-6.12.1/net/rxrpc/ |
| D | call_accept.c | 56 /* We don't need more conns and peers than we have calls, but on the in rxrpc_service_prealloc_one()
58 * than calls. in rxrpc_service_prealloc_one()
95 /* Now it gets complicated, because calls get registered with the in rxrpc_service_prealloc_one()
111 pp = &rx->calls.rb_node; in rxrpc_service_prealloc_one()
133 rb_insert_color(&call->sock_node, &rx->calls); in rxrpc_service_prealloc_one()
142 list_add_tail_rcu(&call->link, &rxnet->calls); in rxrpc_service_prealloc_one()
158 * Allocate the preallocation buffers for incoming service calls. These must
188 /* Make sure that there aren't any incoming calls in progress before we in rxrpc_discard_prealloc()
256 /* #calls >= #conns >= #peers must hold true. */ in rxrpc_alloc_incoming_call()
323 * retainer ref obtained from the backlog buffer. Prealloc calls for userspace
[all …]
|
| /linux-6.12.1/Documentation/arch/arm/ |
| D | kernel_mode_neon.rst | 11 * Put kernel_neon_begin() and kernel_neon_end() calls around the calls into your
60 If latency is a concern, it is possible to put back to back calls to
62 the NEON registers are live. (Additional calls to kernel_neon_begin() should be
83 between calls to these respective functions. Furthermore, GCC may generate NEON
93 * issue the calls to kernel_neon_begin(), kernel_neon_end() as well as the calls
|
| /linux-6.12.1/drivers/md/dm-vdo/ |
| D | statistics.h | 104 /* number of get_vdo_page() calls for read */
106 /* number of get_vdo_page() calls for write */
182 /* Number of post calls that found an existing entry */
184 /* Number of post calls that added a new entry */
186 /* Number of query calls that found an existing entry */
188 /* Number of query calls that added a new entry */
190 /* Number of update calls that found an existing entry */
192 /* Number of update calls that added a new entry */
|
| /linux-6.12.1/arch/m68k/include/asm/ |
| D | floppy.h | 191 static int calls=0; in floppy_hardint() local
201 if(!calls) in floppy_hardint()
230 calls++; in floppy_hardint()
238 pr_info("count=%x, residue=%x calls=%d bytes=%d dma_wait=%d\n", in floppy_hardint()
239 virtual_dma_count, virtual_dma_residue, calls, bytes, in floppy_hardint()
241 calls = 0; in floppy_hardint()
|
| /linux-6.12.1/tools/perf/scripts/python/ |
| D | export-to-postgresql.py | 59 …perf script -s ~/libexec/perf-core/scripts/python/export-to-postgresql.py pt_example branches calls
88 # calls
90 # 'calls' represents function calls and is related to 'samples' by 'call_id' and 'return_id'.
91 # 'calls' is only created when the 'calls' option to this script is specified.
96 # 'calls_paths' is only created when the 'calls' option to this script is specified.
145 # Note that call information is only available if the script's 'calls' option has been used.
147 # Top 10 function calls (not aggregated by symbol):
151 # Top 10 function calls (aggregated by symbol):
165 # Top 10 function calls for a specific symbol (e.g. whose symbol_id is 187):
169 # Show function calls made by function in the same context (i.e. same call path) (e.g. one with cal…
[all …]
|
| /linux-6.12.1/net/ax25/ |
| D | ax25_addr.c | 146 if (ax25cmp(&digi1->calls[i], &digi2->calls[i]) != 0) in ax25digicmp()
194 memcpy(&digi->calls[d], buf, AX25_ADDR_LEN); in ax25_addr_parse()
253 memcpy(buf, &d->calls[ct], AX25_ADDR_LEN); in ax25_addr_build()
293 out->calls[ct] = in->calls[in->ndigi - ct - 1]; in ax25_digi_invert()
296 out->calls[ct].ax25_call[6] |= AX25_HBIT; in ax25_digi_invert()
299 out->calls[ct].ax25_call[6] &= ~AX25_HBIT; in ax25_digi_invert()
|
| /linux-6.12.1/scripts/ |
| D | Makefile.kasan | 4 # Safe for compiler to generate meminstrinsic calls in uninstrumented files.
7 # Don't let compiler generate memintrinsic calls in uninstrumented files
63 # Instrument memcpy/memset/memmove calls by using instrumented __asan_mem*()
82 kasan_params += hwasan-instrument-with-calls=1
89 # Instrument memcpy/memset/memmove calls by using instrumented __hwasan_mem*().
|
| /linux-6.12.1/Documentation/networking/ |
| D | rxrpc.rst | 65 to speed up subsequent calls.
123 billion calls, but only up to four calls may be in progress on a
126 (#) Calls are two-phase and asymmetric: the client sends its request data,
141 set for the lifetime of that connection, and all subsequent calls made
146 (#) Calls use ACK packets to handle reliability. Data packets are also
175 make multiple simultaneous calls to the same service. One server socket
176 may handle calls from many clients.
179 concurrent calls, up to a tunable limit.
189 (#) A client-side connection is only shared between calls if they have
190 the same key struct describing their security (and assuming the calls
[all …]
|
| /linux-6.12.1/Documentation/driver-api/firmware/ |
| D | firmware_cache.rst | 12 calls, automatically behind the scenes.
14 The firmware cache makes using certain firmware API calls safe during a device
15 driver's suspend and resume callback. Users of these API calls needn't cache
49 calls requiring the non-uevent therefore need to implement their own firmware
|