X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fuserprog.texi;h=65932604d7099a7d0ae374a63f9b6e0249e9e723;hb=c36588ec57d9dc7237b3038f1050892f2e9e011b;hp=92959ec06f9e1242328e59688bbf5992099bb314;hpb=1c07a79a63dbbd1f4047bf32046518de6f879d50;p=pintos-anon

diff --git a/doc/userprog.texi b/doc/userprog.texi
index 92959ec..6593260 100644
--- a/doc/userprog.texi
+++ b/doc/userprog.texi
@@ -1045,8 +1045,9 @@ Thus, when the system call handler @func{syscall_handler} gets control,
 the system call number is in the 32-bit word at the caller's stack
 pointer, the first argument is in the 32-bit word at the next higher
 address, and so on.  The caller's stack pointer is accessible to
-@func{syscall_handler} as the @samp{esp} member of the @code{struct
-intr_frame} passed to it.
+@func{syscall_handler} as the @samp{esp} member of the
+@struct{intr_frame} passed to it.  (@struct{intr_frame} is on the kernel
+stack.)
 
 The 80@var{x}86 convention for function return values is to place them
 in the @code{EAX} register.  System calls that return a value can do