Re: [Etherboot-developers] mknbi mkelf -1.9 stack problem.
Brought to you by:
marty_connor,
stefanhajnoczi
|
From: <ke...@us...> - 2002-09-10 11:15:44
|
>mknbi && mkelf assume they will be given a stack pointer that can be >accessed with RELOC as their %ss segment base address. mknbi >handles this better as it calls _real_to_prot before calling _prot_to_real. >With the _real_to_prot call first the stack pointer is mangled into >something that works when etherboot runs at an unexpected address. > >The 32bit entry code does much less mangling of the stack pointer and >breaks more visibly. When 5.1.2+ runs at unexpected address, both >code bases break to some degree. > >I believe this is the primary reason why mkelf fails under 5.1.2+. > >Ken does this sound correct? Yes, there is an unfortunate hidden assumption that it's called from Etherboot running somewhere in 0x9xxxx. >If so when I have a moment I will add the code to switch to a private >internal stack, so this issue will go away, unless someone beats >me to it :) Go for it, I'm swamped this week. It would be good if the internal stack were somewhere safe for 5.0 as well so that nothing will break. |