summaryrefslogtreecommitdiff
path: root/Notes
diff options
context:
space:
mode:
authorrtm <rtm>2006-06-13 15:50:06 +0000
committerrtm <rtm>2006-06-13 15:50:06 +0000
commit0a70d042d04e084da4226e7d0d684dedcae06d78 (patch)
tree3dfa629b4e4b44b399fb13b384ed9b50dd03f997 /Notes
parent70a895f63c504f255a28f63efdcfc6b39b2572c5 (diff)
downloadxv6-labs-0a70d042d04e084da4226e7d0d684dedcae06d78.tar.gz
xv6-labs-0a70d042d04e084da4226e7d0d684dedcae06d78.tar.bz2
xv6-labs-0a70d042d04e084da4226e7d0d684dedcae06d78.zip
more or less take traps/interrupts
Diffstat (limited to 'Notes')
-rw-r--r--Notes8
1 files changed, 8 insertions, 0 deletions
diff --git a/Notes b/Notes
index e5e2c5f..cee3b3d 100644
--- a/Notes
+++ b/Notes
@@ -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?