Lines Matching refs:calls

7 limited part of the memory map. System calls (may) allow user threads to
10 When defining system calls, it is very important to ensure that access to the
18 supervisor mode should never be exposed as system calls. Reserve these
21 This section describes how to declare new system calls and discusses a few
27 All system calls have the following components:
33   What gets generated is an inline function which either calls the
77 calls to generate. However, any generated system calls that don't actually have
80 unimplemented system calls. Data type definitions for APIs should not have
83 Any header file that declares system calls must include a special generated
136   code runs in user mode and system calls are unconditionally made.
197 implementing system calls must implement the seven inline functions
216 Some system calls may have more than six arguments, but number of arguments
223 System calls return ``uintptr_t`` type value that is C casted, by wrapper, to
255 system call and jump into it. This in turn calls the verification function.
343 All system calls are dispatched to a verifier function with a prefixed
371 Parameters passed to system calls by reference require special handling,
444 Many system calls pass in structures or even linked data structures. All should
561 When verifying system calls, it's important to note which kinds of verification
566 #. For system calls that are defined but not compiled, invocations of these
567    missing system calls are routed to :c:func:`handler_no_syscall()` which
576 #. Most system calls take kernel object pointers as an argument, checked either
597    be exposed as system calls. Some driver subsystem APIs may take optional
620 * Various system calls related to logging invoke :c:macro:`K_OOPS()`
648 Functions for invoking system calls are defined in