Read curproc from cpu structure, but be careful because after a schedule event

myproc() points to a different thread.

   myproc();
   sched();
   myproc();  // this proc maybe different than the one before sched

Thus, in a function that operates on one thread better to retrieve the
current process once at the start of the function.

1 files changed, 1 insertions, 3 deletions

diff --git a/vm.c b/vm.c
index cb159ad..d1640e8 100644
--- a/vm.c
+++ b/vm.c
@@ -27,13 +27,11 @@ seginit(void)
   c->gdt[SEG_UCODE] = SEG(STA_X|STA_R, 0, 0xffffffff, DPL_USER);
   c->gdt[SEG_UDATA] = SEG(STA_W, 0, 0xffffffff, DPL_USER);
   c->cpu = c;
+  c->proc = 0;
   // Map cpu and proc -- these are private per cpu.
   c->gdt[SEG_KCPU] = SEG(STA_W, &c->cpu, 4, 0);
   lgdt(c->gdt, sizeof(c->gdt));
   loadgs(SEG_KCPU << 3);
-  // Initialize cpu-local storage.
-  // setcpu(c);
-  setproc(0);
 }
 
 // Return the address of the PTE in page table pgdir