Lines Matching full:we

26 /* We define macro's for registers which have a fixed
79 	/* Compute what the new %wim will be if we save the
106 	 * Basically if we are here, this means that we trapped
125 	rett	%t_npc			! we are done
137 	 * %glob_tmp.  We cannot set the new %wim first because we
139 	 * a trap (traps are off, we'd get a watchdog wheee)...
173 	/* The users stack is ok and we can safely save it at
183 	/* We have spilled successfully, and we have properly stored
199 	/* Wheee, user has trashed his/her stack.  We have to decide
200 	 * how to proceed based upon whether we came from kernel mode
201 	 * or not.  If we came from kernel mode, toss the window into
203 	 * and we could be in an interrupt handler so timing is crucial.
204 	 * If we came from user land we build a full stack frame and call
225 		/* Compute new user window mask.  What we are basically
227 		 * time and the one we attempted to throw onto the users
259 	 * doesn't then we never get this far as the process will
268 	/* The kernel provoked a spill window trap, but the window we
270 	 * stack pointer.  We need to be quick, so we throw it into
271 	 * a per-process window buffer until we can properly handle
295  * make usage of glob_tmp and t_psr so we leave them defined.
310 	 * works for all current v8/srmmu implementations, we'll
317 	/* Because of SMP concerns and speed we play a trick.
318 	 * We disable fault traps in the MMU control register,
324 	 * up in kernel vma, then we would succeed for the 'wrong'
360 	andcc	%glob_tmp, 0x2, %g0			! did we fault?
365 	b	spwin_user_stack_is_bolixed + 0x4	! we faulted, ugh