-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Process abstraction #6
Comments
I volunteer to work on this. Anybody else game? |
I will also work on this. |
So, we've hit a wall with the process abstraction. Currently, we have a rudimentary pcb struct implemented. Assuming the major pieces of a process abstraction (e.g. the program code and data) exist in main memory, where does the input, specifically the address of the executable image come from? I'm assuming from the ELF group, perhaps? |
I would say the "process support" should allocate this memory as an initial address space. ELF parsing and loading should map the sections into this given memory region so that the dispatcher (i.e., the initial implementation of context-switching) can start a process of the program image. Does this make sense? |
We need a proper process abstraction, i.e., some implementation of a PCB and some initial implementation of context-switching into a process.
The text was updated successfully, but these errors were encountered: