Lines Matching refs:arguments

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,
73 it's preferred to encapsulate the majority of the arguments into a structure
161 arguments (i.e. parameter 1, 3, 5), to allow use of contiguous pairs of 32-bit
162 registers.  (This concern does not apply if the arguments are part of a
192 of arguments to the system call, and the macro takes the system call name
193 followed by the (type, name) pairs for the parameters as arguments.  Using
280 system call's arguments has a type that is explicitly 64-bit even on a 32-bit
286 does *not* need a compatibility layer; for example, splice(2)'s arguments of
309 arguments from a 32-bit invocation.
357 the new system call.  There's a choice here: the layout of the arguments
487    arguments: https://lwn.net/Articles/311630/
513    arguments should encapsulate those arguments in a struct, which includes a
521  - Discussion from Matthew Wilcox about restrictions on 64-bit arguments: