Updated to use Bochs 2.6.11

[pintos-anon] / doc / vm.tmpl

diff --git a/doc/vm.tmpl b/doc/vm.tmpl
index 987e0573cce7131d0352b8186707baefd57976d4..9e6a9a56a36cdebdb7430548da219303812f19e0 100644 (file)
--- a/doc/vm.tmpl
+++ b/doc/vm.tmpl
@@ -1,8 +1,8 @@
-                           +---------------------------+
-                   |           CS 140          |
-                   | PROJECT 3: VIRTUAL MEMORY |
-                   |      DESIGN DOCUMENT      |
-                   +---------------------------+
+            +---------------------------+
+            |          CS 140          |
+            | PROJECT 3: VIRTUAL MEMORY |
+            |      DESIGN DOCUMENT      |
+            +---------------------------+
 
 ---- GROUP ----
 
@@ -19,10 +19,10 @@ FirstName LastName <email@domain.example>
 
 >> Please cite any offline or online sources you consulted while
 >> preparing your submission, other than the Pintos documentation, course
->> text, and lecture notes.
+>> text, lecture notes, and course staff.
 
-                       PAGE TABLE MANAGEMENT
-                       =====================
+            PAGE TABLE MANAGEMENT
+            =====================
 
 ---- DATA STRUCTURES ----
 
@@ -32,8 +32,8 @@ FirstName LastName <email@domain.example>
 
 ---- ALGORITHMS ----
 
->> A2: Describe your code for locating the frame, if any, that
->> contains the data of a given page.
+>> A2: In a few paragraphs, describe your code for accessing the data
+>> stored in the SPT about a given page.
 
 >> A3: How does your code coordinate accessed and dirty bits between
 >> kernel and user virtual addresses that alias a single frame, or
@@ -49,8 +49,8 @@ FirstName LastName <email@domain.example>
 >> A5: Why did you choose the data structure(s) that you did for
 >> representing virtual-to-physical mappings?
 
-                      PAGING TO AND FROM DISK
-                      =======================
+               PAGING TO AND FROM DISK
+               =======================
 
 ---- DATA STRUCTURES ----
 
@@ -103,8 +103,8 @@ FirstName LastName <email@domain.example>
 >> where your design falls along this continuum and why you chose to
 >> design it this way.
 
-                        MEMORY MAPPED FILES
-                        ===================
+             MEMORY MAPPED FILES
+             ===================
 
 ---- DATA STRUCTURES ----
 
@@ -130,8 +130,8 @@ FirstName LastName <email@domain.example>
 >> implementation either does or does not share much of the code for
 >> the two situations.
 
-                          SURVEY QUESTIONS
-                          ================
+               SURVEY QUESTIONS
+               ================
 
 Answering these questions is optional, but it will help us improve the
 course in future quarters.  Feel free to tell us anything you