X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fuserprog.texi;h=9db073776ab70c7fadb9e711325b991a23e5e552;hb=d64618b9f5ecb25d4805650a85cafea0bbe95b05;hp=a92697d1b4fe209cbe78b6a2d2b6965bcac41854;hpb=5b670fb86ef37f5a81188e940e5fe1b04b5824af;p=pintos-anon

diff --git a/doc/userprog.texi b/doc/userprog.texi
index a92697d..9db0737 100644
--- a/doc/userprog.texi
+++ b/doc/userprog.texi
@@ -516,9 +516,9 @@ recommend against modifying code in the @file{filesys} directory.}
 
 We have provided you a user-level function for each system call in
 @file{lib/user/syscall.c}.  These provide a way for user processes to
-invoke each system call from a C program.  Each of them calls an
-assembly language routine in @file{lib/user/syscall-stub.S}, which in
-turn invokes the system call interrupt and returns.
+invoke each system call from a C program.  Each uses a little inline
+assembly code to invoke the system call and (if appropriate) returns the
+system call's return value.
 
 When you're done with this part, and forevermore, Pintos should be
 bulletproof.  Nothing that a user program can do should ever cause the