Lines Matching full:the

3  * to handle signals occurring at the same time as system calls.
8  * This work is licensed under the terms of the GNU GPL, version 2 or later.
9  * See the COPYING file in the top-level directory.
17         /* This is the entry point for making a system call. The calling
18          * convention here is that of a C varargs function with the
19          * first argument an 'int *' to the signal_pending flag, the
20          * second one the system call number (as a 'long'), and all further
25         /* This saves a frame pointer and aligns the stack for the syscall.
26          * (It's unclear if the syscall ABI has the same stack alignment
27          * requirements as the userspace function call ABI, but better safe than
36          * The syscall calling convention isn't the same as the C one:
40          *               and return the result in rax
41          * and the syscall instruction needs
44          *               and returns the result in rax
50         /* and the syscall arguments */
58         /* This next sequence of code works in conjunction with the
60          * and the interrupted PC is anywhere between 'safe_syscall_start'
62          * The code sequence must therefore be able to cope with this, and
63          * the syscall instruction must be the final one in the sequence.
66         /* if signal_pending is non-zero, don't do the call */
72         /* code path for having successfully executed the syscall */
95         /* code path when we didn't execute the syscall */