ilo-pona/xv6-65oo2
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Activity
1331 commits 1 branch 0 tags 18 MiB
Commit graph

16 commits

Author SHA1 Message Date
Robert Morris bc943c2309 don't over-lock in exit() 2020-11-05 07:32:10 -05:00
Robert Morris 8d4fbc6e2a Frans' proc_lock. 2020-11-03 15:02:08 -05:00
Robert Morris 8b9b799937 modify each page in usertests countfree() 
get rid of static for walk() and freewalk()
 2020-08-07 05:32:48 -04:00
Robert Morris 3b053f5d58 cpu->scheduler -> cpu->context to reduce confusion 2020-07-17 16:40:57 -04:00
Robert Morris d6dad42aaf rename p->tf to p->trapframe, for consistency with p->context 2020-07-17 16:29:52 -04:00
Robert Morris 56583b1402 updated alarmtest 2019-10-03 15:02:19 -04:00
Frans Kaashoek 7e6c37e67e Support exit status for exit/wait 
One test case for returning a exit status
Passes usertests, but haven't used it to simplify tests
 2019-09-10 12:30:10 -04:00
Robert Morris ea95a6654c trampin -> uservec 
trampout -> userret
 2019-07-26 04:53:46 -04:00
Robert Morris a77287e924 no more PAGEBREAK 2019-07-24 13:33:43 -04:00
Robert Morris 54178ad94d simplify kernel mapping calls 2019-07-23 12:17:17 -04:00
Robert Morris 6b379e4707 -MD and TRAPFRAME 2019-07-22 14:54:40 -04:00
Robert Morris c0266a877a document which proc fields are protected by p->lock 2019-07-10 09:28:00 -04:00
Robert Morris 9981bb2270 tweak some comments. 2019-07-10 08:57:51 -04:00
Robert Morris 9d34838b4f holding p->lock all the way through state=RUNNABLE means we don't need EMBRYO 2019-07-08 11:11:00 -04:00
Frans Kaashoek 67702cf706 Checkpoint switching to per-process locks, in attempt clarify xv6's 
locking plan, which is a difficult to understand because ptable lock
protects many invariants.  This implementation has a bug: once in a
while xv6 unlocks a proc lock that is locked by another core.
 2019-07-02 09:14:47 -04:00
Robert Morris 5753553213 separate source into kernel/ user/ mkfs/ 2019-06-11 09:57:14 -04:00
Renamed from proc.h (Browse further)