Lines Matching refs:that

2 free to update it with notes about any area that is not clear.
9 asking for deadlock.  Also the state of structures that are protected
24 * Slave cpus that receive the MCA interrupt call down into SAL, they
29   sends an unmaskable INIT event to the slave cpus that have not
36   (and does) modify TP.  It is allowed to do that as long as it resets
42   assume that the kernel stack is in a fit state to be used.  Mainly
50   the kernel stack[1].  So switching to a new kernel stack means that
52   assume that current points into the struct task, switching to a new
60   tasks.  The only way to do that on ia64 is to call the unwinder,
66   knows how to start unwinding it.  The tasks that received an MCA or
68   tasks.  But (and its a big but), the cpus that received the MCA
72   tasks are on a cpu and which are not.  Hence each slave cpu that
74   set_curr_task(), so the monarch can tell that the _original_ task is
75   no longer running on that cpu.  That gives us a decent chance of
79   nested error, we want diagnostics on the MCA/INIT handler that
80   failed, not on the task that was originally running.  Again this
82   own stack as running on that cpu.  Then a recursive error gets a
87     chained stacks like i386 interrupt stacks.  But that required
90     Mosberger vetoed that approach.  Which meant that separate kernel
102 At least that is what is supposed to happen.  Alas there are broken
104 drive them all as slaves.  Some drive one cpu as monarch, wait for that
153 MCA/INIT never tries to backtrace user space.  Which means that the OS
162 How do we get a backtrace on the tasks that were running when MCA/INIT
177 How do we identify the tasks that were running when MCA/INIT was
182 the previous task.  You can look at that field in dumps or debuggers.
187 MCA_SOS_OFFSET.  You can get that value from mca_asm.h or calculate it
193 'MCA 12159' means that pid 12159 was running when the MCA was