Searched full:calls (Results 1 – 25 of 534) sorted by relevance
12345678910>>...22
| /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
|
| /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 …]
|
| /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.
|
| /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 …]
|
| /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
|
| /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.
|
| /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
|
| /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 …]
|
| /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
|
| /Documentation/userspace-api/media/v4l/ |
| D | planar-apis.rst | 19 Some of the V4L2 API calls and structures are interpreted differently,
22 corresponding buffer type to its ioctl calls. Multi-planar versions of
33 the multi-planar API and a multi-planar format. Multi-planar API calls
39 Calls that distinguish between single and multi-planar APIs
|
| D | libv4l-introduction.rst | 75 just pass calls through.
86 of just providing the raw output of the device, it enhances the calls in
90 In most cases, libv4l2 just passes the calls directly through to the
91 v4l2 driver, intercepting the calls to
171 This library intercepts calls to
176 ``LD_PRELOAD=/usr/lib/v4l1compat.so``. It also emulates V4L1 calls via V4L2
|
| /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()
|
| /Documentation/arch/arm/samsung/ |
| D | gpio.rst | 9 specific calls provided alongside the drivers/gpio core.
16 specific calls for the items that require Samsung specific handling, such
|
| /Documentation/ABI/removed/ |
| D | sysfs-selinux-checkreqprot | 12 calls instead of the actual protection applied by the kernel.
23 check the actual protections being applied upon mmap/mprotect calls.
|
| /Documentation/driver-api/phy/ |
| D | phy.rst | 133 consumer calls on the NULL phy become NOPs. That is the release calls,
134 the phy_init() and phy_exit() calls, and phy_power_on() and
135 phy_power_off() calls are all NOP when applied to a NULL phy. The NULL
138 Order of API calls
141 The general order of calls should be::
193 device created by this subsystem will be a child of the device that calls
|
| /Documentation/userspace-api/ |
| D | seccomp_filter.rst | 8 A large number of system calls are exposed to every userland process
10 As system calls change and mature, bugs are found and eradicated. A
12 of available system calls. The resulting set reduces the total kernel
17 incoming system calls. The filter is expressed as a Berkeley Packet
21 filtering of system calls using a filter program language with a long
40 system calls in socketcall() is allowed, for instance) which could be
335 The vDSO can cause some system calls to run entirely in userspace,
343 legacy variants on vDSO calls.) Currently, emulated vsyscalls will
370 instructions at ``0xF...F600{0,4,8,C}00`` will not be system calls in these
375 syscalls. New code will use the vDSO, and vDSO-issued system calls
[all …]
|
| /Documentation/admin-guide/ |
| D | highuid.rst | 31 - Need to validate that OS emulation calls the 16-bit UID
33 uses the 32-bit UID system calls properly otherwise.
40 (need to support whatever new 32-bit UID system calls are added to
|
| /Documentation/filesystems/ |
| D | inotify.rst | 86 device file or a family of new system calls. We decided to implement a
87 family of system calls because that is the preferred approach for new kernel
89 and ioctl(2) or a couple of new system calls. System calls beat ioctls.
|
| /Documentation/security/keys/ |
| D | request-key.rst | 54 The request_key_with_auxdata() calls is like the request_key_tag() call, except
78 1) Process A calls request_key() [the userspace syscall calls the kernel
155 firstly calls key_permission(SEARCH) on the keyring it's starting with,
159 matches the criteria specified, calls key_permission(SEARCH) on it to see
165 searching. It calls key_permission(SEARCH) on each keyring, and if this
|
| /Documentation/networking/ |
| D | msg_zerocopy.rst | 9 The MSG_ZEROCOPY flag enables copy avoidance for socket send calls.
20 underlying copy avoidance mechanism to common socket send calls.
96 feature is implemented as a flag. It is safe to mix calls with the flag
112 UINT_MAX calls.
141 every couple of send calls.
146 a zero error code, however, to not block send and recv calls.
183 as explained before, to avoid blocking read and write system calls on
|
| 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 …]
|
| /Documentation/arch/arm64/ |
| D | tagged-pointers.rst | 29 - pointer arguments to system calls, including pointers in structures
30 passed to system calls,
44 passing non-zero address tags to the kernel via system calls is
|
| /Documentation/dev-tools/kunit/api/ |
| D | functionredirection.rst | 32 A simpler way to intercept and replace some of the function calls is to use
39 Static stubs are a way of redirecting calls to one function (the "real"
102 the replacement function instead. Such calls may be buried deep in the
144 /* In the test case, redirect calls for the duration of the test */
|
| /Documentation/locking/ |
| D | futex-requeue-pi.rst | 24 Consider the simplified glibc calls::
82 necessary changes inside the existing calls rather than creating new
83 calls for the PI cases. Similar changes are needed for
101 Two new system calls provide the kernel<->user interface to
|
| /Documentation/trace/ |
| D | ftrace-design.rst | 61 the mcount function normally calls __mcount_internal -- the first argument is
65 For example, if the function foo() calls bar(), when the bar() function calls
127 calls the arch-specific function prepare_ftrace_return. Neither of these
214 that calls prepare_ftrace_return(), pass the frame pointer as the 3rd argument.
229 - Put the trace_sys_enter() and trace_sys_exit() tracepoints calls from ptrace
232 of addresses of the system calls, implement an arch_syscall_addr to return
234 - If the symbol names of the system calls do not match the function names on
367 at that location to support the new function calls you'll be inserting. Some
|
12345678910>>...22