ELF loading and the stack

[StereoRocker]

Hi everyone,

I've recently started getting back into OSDev, and I'm at a point with my kernel where I can start implementing ELF loading.
There's one thing that's tripping me up, and that's finding out information about the stack with regards to ELF files.

I need to know if it's the kernel's responsibility to allocate a stack to the process and ensure that it's valid and active, or whether a suitable stack is defined within the program headers and the _start function sets this up accordingly.

(I have searched to see if this topic has been posted previously, but didn't find anything. I apologise if it indeed has been asked already!)

Thanks,
NFSGamer

[embryo2]

I need to know if it's the kernel's responsibility to allocate a stack to the process and ensure that it's valid and active, or whether a suitable stack is defined within the program headers and the _start function sets this up accordingly.

It's a design issue. And that's why it means you have to decide it on your own.

Generally the kernel manages processes and the management includes process's stack and some data structures. But you can implement a system where some external entity has created the stack and data structures. It's, of course, looks very inefficient, because you lose control over many essential parts of your system. But if you want to create something "new" then why not?

[StereoRocker]

I see. I think I'll go with kernel managed stack space then. Though it would be interesting to see the alternative put to use.

Thanks for your help!