Lines Matching full:exit

1 Entry/exit handling for exceptions, interrupts, syscalls and KVM
22 for entry code before RCU starts watching and exit code after RCU stops
55 All non-instrumentable entry/exit code sections before and after the RCU
106 exit_to_user_mode() is called last on exit.
116 guest and returns to the kernel on exit.
126 Do not nest KVM entry/exit transitions because doing so is nonsensical.
131 Interrupts entry and exit handling is slightly more complex than syscalls
135 and exit handling is exactly the same as for syscalls.
138 exit handling is slightly different. RCU state is only updated when the
188 disabled, interrupt nesting is common from an entry/exit perspective. For
189 example, softirq handling happens within an irqentry_{enter,exit}() block with
193 Interrupt entry/exit code doesn't strictly need to handle reentrancy, since it
220 The exit counterpart irqentry_nmi_exit() does the reverse operation in the
224 operation on enter and the last operation on exit. The reason is that both
226 preemption count modification in the NMI entry/exit case must not be