course_os icon indicating copy to clipboard operation
course_os copied to clipboard

Published 20 hours ago • verified publisher icon rellermeyer

Process abstraction

Open rellermeyer opened this issue 10 years ago • 4 comments

We need a proper process abstraction, i.e., some implementation of a PCB and some initial implementation of context-switching into a process.

rellermeyer avatar Mar 08 '14 05:03 rellermeyer

I volunteer to work on this. Anybody else game?

ronso-rage avatar Mar 17 '14 23:03 ronso-rage

I will also work on this.

bigfuss avatar Mar 19 '14 21:03 bigfuss

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?

ronso-rage avatar Mar 21 '14 20:03 ronso-rage

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?

rellermeyer avatar Mar 23 '14 05:03 rellermeyer