diff options
| author | rsc <rsc> | 2007-08-08 08:57:37 +0000 |
|---|---|---|
| committer | rsc <rsc> | 2007-08-08 08:57:37 +0000 |
| commit | 00d0f794cfd7a1df3b73f28028c8768bae3fef09 (patch) | |
| tree | 2b955fe2559c1a26b1ce7afec43fb6695dd852f6 /BUGS | |
| parent | bda5186c0d6baee0f45b543513ffb0f629c9f348 (diff) | |
| download | xv6-labs-00d0f794cfd7a1df3b73f28028c8768bae3fef09.tar.gz xv6-labs-00d0f794cfd7a1df3b73f28028c8768bae3fef09.tar.bz2 xv6-labs-00d0f794cfd7a1df3b73f28028c8768bae3fef09.zip | |
fix various bugs
Diffstat (limited to 'BUGS')
| -rw-r--r-- | BUGS | 12 |
1 files changed, 0 insertions, 12 deletions
@@ -12,15 +12,6 @@ main.c: cpus[0] -> cpus[bcpu] proc.c: - comment at top of scheduler() should say - via longjmp back to the scheduler - not - via longjmp back to the top of scheduler - - sched should panic if state == RUNNING. - - forkret comment should say "Return" not "return" - as a consequence of the implementation of proc_kill, any loop calling sleep should check for p->killed and be able to break out with an error return. @@ -28,9 +19,6 @@ proc.c: can swap procdump up after proc_kill and then have proc_exit and proc_wait on same sheet - proc_exit should wake up proc[1] if any - reparenting was done. - sched -> switch2scheduler? or just switch? factor out switching and scheduling code from process code |