Do not disable IRQs to protect cur_ctx
authorBarret Rhoden <brho@cs.berkeley.edu>
Mon, 7 Dec 2015 23:36:28 +0000 (18:36 -0500)
committerBarret Rhoden <brho@cs.berkeley.edu>
Thu, 10 Dec 2015 16:23:30 +0000 (11:23 -0500)
commitaa8bb7c870998e0474d8157295ded1863e86d628
tree7280808fba9878e6f07abec02af9b65253238e17
parent72cca7bcef62df468b2bf655def89a8bd330df84
Do not disable IRQs to protect cur_ctx

Back in the day, current_ctx needed to be protected against interrupts.
That was when the process management kernel messages were IMMEDIATE.
Nowadays, they are ROUTINE, and you don't need IRQ protections.

I think.

Signed-off-by: Barret Rhoden <brho@cs.berkeley.edu>
kern/src/schedule.c
kern/src/syscall.c