Imbus/xv6-riscv-kernel
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

more or less take traps/interrupts

Browse source
This commit is contained in:
rtm 2006-06-13 15:50:06 +00:00
parent 70a895f63c
commit 0a70d042d0
7 changed files with 791 additions and 70 deletions
Download patch file Download diff file Expand all files Collapse all files

8
Notes
View file

@ -65,3 +65,11 @@ perhaps have fixed-size stack, put it in the data segment?
oops, if kernel stack is in contiguous user phys mem, then moving
users' memory (e.g. to expand it) will wreck any pointers into the
kernel stack.
do we need to set fs and gs? so user processes can't abuse them?
setupsegs() may modify current segment table, is that legal?
trap() ought to lgdt on return, since currently only done in swtch()
protect hardware interrupt vectors from user INT instructions?