X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fvm.texi;fp=doc%2Fvm.texi;h=c2943cacecaaac2d698176ee8969b195c1518a46;hb=d158a7cd545fa8dd35dba91935029465eedff0da;hp=25135f067efb66cee2aa2016a9ed5e5ea9e64e9f;hpb=594421de07283cdf4cce7226eb2c468c7ea2fedd;p=pintos-anon

diff --git a/doc/vm.texi b/doc/vm.texi
index 25135f0..c2943ca 100644
--- a/doc/vm.texi
+++ b/doc/vm.texi
@@ -714,6 +714,12 @@ process.  If you carefully designed your data structures,
 sharing of read-only pages should not make this part significantly
 harder.
 
+@item How do we resume a process after we have handled a page fault?
+
+Returning from @func{page_fault} resumes the current user process
+(@pxref{Internal Interrupt Handling}).
+It will then retry the instruction to which the instruction pointer points.
+
 @item Does the virtual memory system need to support data segment growth?
 
 No.  The size of the data segment is determined by the linker.  We still