Lines Matching +full:os +full:- +full:code +full:- +full:offset

2 An ad-hoc collection of notes on IA64 MCA and INIT processing
7 ---
10 the OS is in any state.  Including when one of the cpus is already
15 ---
48   have to use their own, per-cpu stacks.  The MCA/INIT stacks are
97 ---
102 slaves.  All the OS INIT handlers are entered at approximately the same
103 time.  The OS monarch prints the state of all tasks and returns, after
109 cpu to return from the OS then drive the rest as slaves.  Some versions
110 of SAL cannot even cope with returning from the OS, they spin inside
111 SAL on resume.  The OS INIT code has workarounds for some of these
112 broken SAL symptoms, but some simply cannot be fixed from the OS side.
114 ---
123 special code to cope with our inability to take any locks.
125 ---
148 ---
151 space code?
154 entry to the OS and are restored from there on return to SAL, so user
156 OS has no idea what unwind data is available for the user space stack,
157 MCA/INIT never tries to backtrace user space.  Which means that the OS
159 i.e. the OS does not copy pt_regs and switch_stack to the user space
160 stack.  Also the OS has no idea how big the user space RSE and memory
164 ---
179 ---
185 state, then sos->prev_task on the MCA/INIT stack is updated to point to
190 The sos data is always in the MCA/INIT handler stack, at offset
192 as KERNEL_STACK_SIZE - sizeof(struct pt_regs) - sizeof(struct