Lines Matching full:state

4 All transitions between execution domains require state updates which are
5 subject to strict ordering constraints. State updates are required for the
23 watching. In addition, many architectures must save and restore register state,
52 restrictions and is useful to protect e.g. state switching which would
56 state transitions must run with interrupts disabled.
62 after establishing low-level architecture-specific state and stack frames. This
82 establishes state in the following order:
95 that it invokes exit_to_user_mode() which again handles the state
120 The state operations have the same ordering.
138 exit handling is slightly different. RCU state is only updated when the
151 	state = irqentry_enter(regs);
161 	irqentry_exit(regs, state);
168 return true, handles NOHZ tick state and interrupt time accounting. This
173 count update and eventually handles soft interrupts and NOHZ tick state.
180 preemption count has not yet been updated with the HARDIRQ_OFFSET state.
202 the state.
204 State changes for debug exceptions and machine-check exceptions depend on
209 NMIs and other NMI-like exceptions handle state transitions without
212 The state update on entry is handled in irqentry_nmi_enter() which updates
213 state in the following order:
236 	state = irqentry_nmi_enter(regs);
256 		state = irqentry_enter(regs);
262 		irqentry_exit(regs, state);
264   		state = irqentry_nmi_enter(regs);
270 		irqentry_nmi_exit(regs, state);
278 while handling an NMI. So NMI entry code has to be reentrant and state updates