On Thu, 27 Jan 2005 18:08:18 -0800, David Mosberger <davidm@napali.hpl.hp.com> wrote: >>>>>> On Thu, 20 Jan 2005 21:26:18 +1100, Keith Owens <kaos@sgi.com> said: > > Keith> Unwinding across firmware is not an issue here, we have two > Keith> views of the MCA/INIT context. One view is "how to return to > Keith> SAL?", that data is stored outside the stack. The other view > Keith> is "what was the cpu doing when the event occurred?". It is > Keith> the latter that I am working on. > >How is this different from the "unw_init_from_interruption" call that >we're doing in mca.c:init_handler_platform()? That only works for the INIT call which uses the current bspstore, MCA uses its own bspstore. The kernel unwinder is not set up to switch bspstore between two kernel stacks, only between kernel and user space. The INIT call will change to its own bspstore once we use the separate INIT and MCA stacks for each cpu. - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Thu Jan 27 22:05:41 2005
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:35 EST