Lines Matching refs:handler

41   - execution is interruptible and preemptible (an fsys-mode handler
77 * How to write an fsyscall handler
83 normal Linux system call handler.  For performance-critical system
88 The entry and exit-state of an fsyscall handler is as follows:
90 ** Machine state on entry to fsyscall handler:
102 ** Required machine state on exit to fsyscall handler:
104  - r11	  = saved ar.pfs (as passed into the fsyscall handler)
105  - r15	  = system call number (as passed into the fsyscall handler)
106  - r32-r39 = system call arguments (as passed into the fsyscall handler)
107  - b6	  = return address (as passed into the fsyscall handler)
108  - ar.pfs = previous frame-state (as passed into the fsyscall handler)
115    TIF_ALLWORK_MASK flags are set, the handler needs to fall back on
126    contain a NaT value, an fsyscall-handler may return immediately
134    it is not safe to assume that user-level called a handler with the
157 higher overhead.  For example, if an fsyscall-handler could benefit
173 occur.  The trap handler clears PSR.lp again and returns immediately.
187 	restored upon return from an fsys-mode handler.  In other
208 	fsys-mode, the trap-handler modifies the saved machine state
212 	fsyscall-handler, at which point, by definition, a syscall
214 	the fsys-mode handler will return directly to user-level.  This
227 	be taken.  The trap handler then modifies the saved machine
232 	handler performed a speculative load that gets NaTted.  If so, this