Lines Matching refs:arguments

65 For simpler system calls that only take a couple of arguments, the preferred
76 For more sophisticated system calls that involve a larger number of arguments,
77 it's preferred to encapsulate the majority of the arguments into a structure
168 arguments (i.e. parameter 1, 3, 5), to allow use of contiguous pairs of 32-bit
169 registers.  (This concern does not apply if the arguments are part of a
199 number of arguments to the system call, and the macro takes the system call name
200 followed by the (type, name) pairs for the parameters as arguments.  Using
288 system call's arguments has a type that is explicitly 64-bit even on a 32-bit
294 does **not** need a compatibility layer; for example, :manpage:`splice(2)`'s arguments of
317 parse the arguments from a 32-bit invocation.
366 the new system call.  There's a choice here: the layout of the arguments
530    arguments: https://lwn.net/Articles/311630/
558    arguments should encapsulate those arguments in a struct, which includes a
568  - Discussion from Matthew Wilcox about restrictions on 64-bit arguments: