Lines Matching full:nmi

943  * only on return from non-NMI IST interrupts that came
1109 	 * the iretq it performs will take us out of NMI context.
1111 	 * NMI is using the top of the stack of the previous NMI. We
1112 	 * can't let it execute because the nested NMI will corrupt the
1113 	 * stack of the previous NMI. NMI handlers are not re-entrant
1120 	 *  is an NMI stack.
1121 	 *  If the variable is not set and the stack is not the NMI
1127 	 *    o Continue processing the NMI
1128 	 *  If the variable is set or the previous stack is the NMI stack:
1130 	 *    o return back to the first NMI
1132 	 * Now on exit of the first NMI, we first clear the stack variable
1133 	 * The NMI stack will tell any nested NMIs at that point that it is
1135 	 * a nested NMI that updated the copy interrupt stack frame, a
1137 	 * NMI.
1155 	 * NMI from user mode.  We need to run on the thread stack, but we
1162 	 * stacks lest we corrupt the "NMI executing" variable.
1187 	 * done with the NMI stack.
1211 	 * | "NMI executing" variable                                |
1215 	 * | iret RFLAGS      } by a nested NMI to force another     |
1221 	 * | outermost RFLAGS      } NMI processing is done.         |
1233 	 * That will either return for real or it will loop back into NMI
1242 	 * Determine whether we're a nested NMI.
1245 	 * end_repeat_nmi, then we are a nested NMI.  We must not
1247 	 * the outer NMI.  That's okay; the outer NMI handler is
1249 	 * the outer NMI.
1261 	 * Now check "NMI executing".  If it's set, then we're nested.
1262 	 * This will not detect if we interrupted an outer NMI just
1269 	 * Now test if the previous stack was an NMI stack.  This covers
1270 	 * the case where we interrupt an outer NMI after it clears
1271 	 * "NMI executing" but before IRET.  We need to be careful, though:
1272 	 * there is one case in which RSP could point to the NMI stack
1273 	 * despite there being no NMI active: naughty userspace controls
1278 	 * "NMI executing".
1281 	/* Compare the NMI stack (rdx) with the stack we came from (4*8(%rsp)) */
1283 	/* If the stack pointer is above the NMI stack, this is a normal NMI */
1288 	/* If it is below the NMI stack, it is a normal NMI */
1291 	/* Ah, it is within the NMI stack. */
1296 	/* This is a nested NMI. */
1301 	 * iteration of NMI handling.
1324 	/* Make room for "NMI executing". */
1357 	 * If there was a nested NMI, the first NMI's iret will return
1359 	 * nested NMI. The nested NMI checks the interrupted RIP to see
1361 	 * it will just return, as we are about to repeat an NMI anyway.
1363 	 * NMI will update.
1366 	 * we're repeating an NMI, gsbase has the same value that it had on
1368 	 * gsbase if needed before we call exc_nmi().  "NMI executing"
1371 	movq	$1, 10*8(%rsp)		/* Set "NMI executing". */
1387 	 * Everything below this point can be preempted by a nested NMI.
1388 	 * If this happens, then the inner NMI will change the "iret"
1395 	 * as we should not be calling schedule in NMI context.
1396 	 * Even with normal interrupts enabled. An NMI should not be
1442 	 * Clear "NMI executing".  Set DF first so that we can easily
1451 	movq	$0, 5*8(%rsp)		/* clear "NMI executing" */
1455 	 * NMI in kernel after user state is restored. For an unprivileged user
1460 	 * iretq reads the "iret" frame and exits the NMI stack in a