Lines Matching full:nmi
982 * only on return from non-NMI IST interrupts that came
1149 * the iretq it performs will take us out of NMI context.
1151 * NMI is using the top of the stack of the previous NMI. We
1152 * can't let it execute because the nested NMI will corrupt the
1153 * stack of the previous NMI. NMI handlers are not re-entrant
1160 * is an NMI stack.
1161 * If the variable is not set and the stack is not the NMI
1167 * o Continue processing the NMI
1168 * If the variable is set or the previous stack is the NMI stack:
1170 * o return back to the first NMI
1172 * Now on exit of the first NMI, we first clear the stack variable
1173 * The NMI stack will tell any nested NMIs at that point that it is
1175 * a nested NMI that updated the copy interrupt stack frame, a
1177 * NMI.
1195 * NMI from user mode. We need to run on the thread stack, but we
1202 * stacks lest we corrupt the "NMI executing" variable.
1227 * done with the NMI stack.
1252 * | "NMI executing" variable |
1256 * | iret RFLAGS } by a nested NMI to force another |
1262 * | outermost RFLAGS } NMI processing is done. |
1274 * That will either return for real or it will loop back into NMI
1283 * Determine whether we're a nested NMI.
1286 * end_repeat_nmi, then we are a nested NMI. We must not
1288 * the outer NMI. That's okay; the outer NMI handler is
1290 * resume the outer NMI.
1302 * Now check "NMI executing". If it's set, then we're nested.
1303 * This will not detect if we interrupted an outer NMI just
1310 * Now test if the previous stack was an NMI stack. This covers
1311 * the case where we interrupt an outer NMI after it clears
1312 * "NMI executing" but before IRET. We need to be careful, though:
1313 * there is one case in which RSP could point to the NMI stack
1314 * despite there being no NMI active: naughty userspace controls
1319 * "NMI executing".
1322 /* Compare the NMI stack (rdx) with the stack we came from (4*8(%rsp)) */
1324 /* If the stack pointer is above the NMI stack, this is a normal NMI */
1329 /* If it is below the NMI stack, it is a normal NMI */
1332 /* Ah, it is within the NMI stack. */
1337 /* This is a nested NMI. */
1342 * iteration of NMI handling.
1365 /* Make room for "NMI executing". */
1398 * If there was a nested NMI, the first NMI's iret will return
1400 * nested NMI. The nested NMI checks the interrupted RIP to see
1402 * it will just return, as we are about to repeat an NMI anyway.
1404 * NMI will update.
1407 * we're repeating an NMI, gsbase has the same value that it had on
1409 * gsbase if needed before we call exc_nmi(). "NMI executing"
1412 movq $1, 10*8(%rsp) /* Set "NMI executing". */
1428 * Everything below this point can be preempted by a nested NMI.
1429 * If this happens, then the inner NMI will change the "iret"
1436 * as we should not be calling schedule in NMI context.
1437 * Even with normal interrupts enabled. An NMI should not be
1485 * Clear "NMI executing". Set DF first so that we can easily
1494 movq $0, 5*8(%rsp) /* clear "NMI executing" */
1497 * iretq reads the "iret" frame and exits the NMI stack in a