projects
/
pintos-anon
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Replace GSX Server support with VMware Player support.
[pintos-anon]
/
doc
/
userprog.texi
diff --git
a/doc/userprog.texi
b/doc/userprog.texi
index 8ed52b1e6aca46b28c40c9d4a962ee95ee28f7d5..fa534d2382ef3007c36a3f809efbe3eaee29be55 100644
(file)
--- a/
doc/userprog.texi
+++ b/
doc/userprog.texi
@@
-20,9
+20,7
@@
assignment. The ``alarm clock'' functionality may be useful in
projects 3 and 4, but it is not strictly required.
You might find it useful to go back and reread how to run the tests
projects 3 and 4, but it is not strictly required.
You might find it useful to go back and reread how to run the tests
-(@pxref{Testing}). In particular, the tests for project 2 (and later
-projects) will probably run faster if you use the qemu emulator, e.g.@:
-via @code{make check PINTOSOPTS='--qemu'}.
+(@pxref{Testing}).
@menu
* Project 2 Background::
@menu
* Project 2 Background::
@@
-692,8
+690,7
@@
Reads @var{size} bytes from the file open as @var{fd} into
@var{buffer}. Returns the number of bytes actually read (0 at end of
file), or -1 if the file could not be read (due to a condition other
than end of file). Fd 0 reads from the keyboard using
@var{buffer}. Returns the number of bytes actually read (0 at end of
file), or -1 if the file could not be read (due to a condition other
than end of file). Fd 0 reads from the keyboard using
-@func{kbd_getc}. (Keyboard input will not work if you pass the
-@option{-v} option to @command{pintos}.)
+@func{input_getc}.
@end deftypefn
@deftypefn {System Call} int write (int @var{fd}, const void *@var{buffer}, unsigned @var{size})
@end deftypefn
@deftypefn {System Call} int write (int @var{fd}, const void *@var{buffer}, unsigned @var{size})
@@
-912,12
+909,6
@@
You can choose whatever suitable types you like for @code{tid_t} and
@code{pid_t}. By default, they're both @code{int}. You can make them
a one-to-one mapping, so that the same values in both identify the
same process, or you can use a more complex mapping. It's up to you.
@code{pid_t}. By default, they're both @code{int}. You can make them
a one-to-one mapping, so that the same values in both identify the
same process, or you can use a more complex mapping. It's up to you.
-
-@item Keyboard input doesn't work.
-
-You are probably passing @option{-v} to @command{pintos}, but
-serial input isn't implemented. Don't use @option{-v} if you
-want to use the shell or otherwise need keyboard input.
@end table
@menu
@end table
@menu