Lines Matching refs:we

52 so. If we mess that up even slightly, we crash.
54 So when we have a secondary entry, already in kernel mode, we *must
55 not* use SWAPGS blindly - nor must we forget doing a SWAPGS when it's
81 If we are at an interrupt or user-trap/gate-alike boundary then we can
83 whether SWAPGS was already done: if we see that we are a secondary
84 entry interrupting kernel mode execution, then we know that the GS
85 base has already been switched. If it says that we interrupted
86 user-space execution then we must do the SWAPGS.
88 But if we are in an NMI/MCE/DEBUG/whatever super-atomic entry context,
90 stack but before we executed SWAPGS, then the only safe way to check
102 that absolutely need the more expensive check for the GS base - and we