| /linux/arch/powerpc/platforms/cell/ |
| H A 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 if (!calls) in spufs_calls_put()
42 BUG_ON(calls != spufs_calls); in spufs_calls_put()
55 static inline void spufs_calls_put(struct spufs_calls *calls) { } in spufs_calls_put() argument
64 CLASS(spufs_calls, calls)(); in DEFINE_CLASS()
[all …]
|
| /linux/net/ax25/ |
| H A 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/arch/m68k/include/asm/ |
| H A D | sun3xflop.h | 122 static int calls=0; in sun3xflop_hardint() local
134 if(!calls) in sun3xflop_hardint()
173 calls++; in sun3xflop_hardint()
185 virtual_dma_count, virtual_dma_residue, calls, bytes, in sun3xflop_hardint()
187 calls = 0; in sun3xflop_hardint()
|
| /linux/Documentation/bpf/standardization/ |
| H A 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/Documentation/mm/ |
| H A 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/Documentation/i2c/ |
| H A 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/include/linux/ |
| H A D | alloc_tag.h | 20 u64 calls; member
146 v.calls += counter->calls; in alloc_tag_read()
193 this_cpu_inc(tag->counters->calls); in alloc_tag_ref_set()
219 this_cpu_dec(tag->counters->calls); in alloc_tag_sub()
|
| /linux/scripts/ |
| H A D | checksyscalls.sh | 78 /* System calls for 32-bit kernels only */
153 /* i386-specific or historical system calls */
226 /* these can be expressed using other calls */
|
| /linux/Documentation/infiniband/ |
| H A 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/arch/arm/tools/ |
| H A D | Makefile | 16 gen-y := $(gen)/calls-oabi.S
17 gen-y += $(gen)/calls-eabi.S
56 $(gen)/calls-%.S: $(syscall) $(systbl) FORCE
|
| /linux/include/kunit/ |
| H A D | run-in-irq-context.h | 109 for (int task_calls = 0, calls = 0; in kunit_run_irq_test() local
110 ((calls < max_iterations) || !allctx) && in kunit_run_irq_test()
118 calls = task_calls + hardirq_calls + softirq_calls; in kunit_run_irq_test()
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | test_cgroup_link.c | 6 int calls = 0; variable
12 __sync_fetch_and_add(&calls, 1); in egress()
|
| /linux/Documentation/crypto/ |
| H A 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/tools/perf/scripts/python/bin/ |
| H A D | export-to-postgresql-report | 19 calls=$3
29 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/export-to-postgresql.py $dbname $columns $calls
|
| H A D | export-to-sqlite-report | 19 calls=$3
29 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/export-to-sqlite.py $dbname $columns $calls
|
| /linux/Documentation/admin-guide/ |
| H A D | workload-tracing.rst | 36 This method of tracing using strace tells us the system calls invoked by
37 the workload and doesn't include all the system calls that can be invoked
39 these system calls that are invoked. As an example, if a workload opens a
53 strace tool can be used to trace system calls made by a process and signals
54 it receives. System calls are the fundamental interface between an
58 us to track all the system calls made by an application. It lists all the
59 system calls made by a process and their resulting output.
111 system calls. This allows us to easily measure the impact of changes,
153 In addition, strace can generate run-time statistics on times, calls, and
160 run in verbose mode gives more detailed information about the system calls
[all …]
|
| /linux/Documentation/arch/arm/ |
| H A 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/arch/sparc/kernel/ |
| H A D | traps_32.c | 202 static int calls; local
272 calls++;
273 if(calls > 2)
298 if(calls > 0)
299 calls=0;
|
| /linux/arch/hexagon/ |
| H A D | Makefile | 14 KBUILD_CFLAGS += -mlong-calls
20 KBUILD_CFLAGS_MODULE += -mlong-calls
|
| /linux/Documentation/driver-api/firmware/ |
| H A 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
|
| /linux/Documentation/process/ |
| H A 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,
318 For most system calls the same 64-bit implementation can be invoked even when
[all …]
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-bench.txt | 288 Suite for evaluating wake calls.
291 Suite for evaluating parallel wake calls.
294 Suite for evaluating requeue calls.
297 Suite for evaluating futex lock_pi calls.
302 Suite for evaluating concurrent epoll_wait calls.
305 Suite for evaluating multiple epoll_ctl calls.
|
| /linux/Documentation/arch/arm/samsung/ |
| H A D | gpio.rst | 9 specific calls provided alongside the drivers/gpio core.
16 specific calls for the items that require Samsung specific handling, such
|
| /linux/Documentation/core-api/ |
| H A 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/net/rxrpc/ |
| H A D | call_object.c | 95 p = rx->calls.rb_node; in rxrpc_find_call_by_user_ID()
363 pp = &rx->calls.rb_node; in rxrpc_new_client_call()
382 rb_insert_color(&call->sock_node, &rx->calls); in rxrpc_new_client_call()
389 list_add_tail_rcu(&call->link, &rxnet->calls); in rxrpc_new_client_call()
587 rb_erase(&call->sock_node, &rx->calls); in rxrpc_release_call()
732 if (!list_empty(&rxnet->calls)) { in rxrpc_destroy_all_calls()
735 while (!list_empty(&rxnet->calls)) { in rxrpc_destroy_all_calls()
736 call = list_entry(rxnet->calls.next, in rxrpc_destroy_all_calls()
|