Lines Matching full:calls

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)
272 For most system calls the same 64-bit implementation can be invoked even when
305 values to 64-bit versions and either calls on to the ``sys_`` version, or both of
310 calls are invoked::
356 Compatibility System Calls (x86)
390 System Calls Returning Elsewhere
393 For most system calls, once the system call is complete the user program
398 However, a few system calls do things differently. They might return to a
428 table will also need to invoke a stub that calls on to the ``compat_sys_``
443 Most of the kernel treats system calls in a generic way, but there is the
485 All new system calls should come with a complete man page, ideally using groff
494 Do not call System Calls in the Kernel
497 System calls are, as stated above, interaction points between userspace and
510 convention for system calls where ``struct pt_regs`` is decoded on-the-fly in a
528 - LWN article from Michael Kerrisk on use of flags argument in system calls:
540 - Architecture-specific requirements for system calls are discussed in the
556 - Suggestion from Greg Kroah-Hartman that it's good for new system calls to
560 - Suggestion from Ingo Molnar that system calls that involve multiple
575 - Recommendation from Linus Torvalds that x32 system calls should prefer