Lines Matching refs:calls

13 the alternatives might be suitable instead.  Although system calls are the
57 together with the corresponding follow-up system calls -- eventfd/eventfd2,
61 For simpler system calls that only take a couple of arguments, the preferred
72 For more sophisticated system calls that involve a larger number of arguments,
117 what it means to use the poll(2) family of system calls on that file
138 (For more details on the rationale of the *at() calls, see the openat(2) man
169 To make new system calls easy to review, it's best to divide up the patchset
199 calls are invoked:
212 note that if multiple new system calls are added in the same merge window,
262 For most system calls the same 64-bit implementation can be invoked even when
294 values to 64-bit versions and either calls on to the sys_ version, or both of
299 calls are invoked:
381 For most system calls, once the system call is complete the user program
386 However, a few system calls do things differently.  They might return to a
415 table will also need to invoke a stub that calls on to the compat_sys_
430 Most of the kernel treats system calls in a generic way, but there is the
471 All new system calls should come with a complete man page, ideally using groff
482  - LWN article from Michael Kerrisk on use of flags argument in system calls:
492  - Architecture-specific requirements for system calls are discussed in the
508  - Suggestion from Greg Kroah-Hartman that it's good for new system calls to
512  - Suggestion from Ingo Molnar that system calls that involve multiple
525  - Recommendation from Linus Torvalds that x32 system calls should prefer