projects
/
pintos-anon
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
264e22e
)
Restore verbatim.
author
Ben Pfaff
<blp@cs.stanford.edu>
Thu, 14 Oct 2004 00:10:41 +0000
(
00:10
+0000)
committer
Ben Pfaff
<blp@cs.stanford.edu>
Thu, 14 Oct 2004 00:10:41 +0000
(
00:10
+0000)
Fix table.
doc/userprog.texi
patch
|
blob
|
history
diff --git
a/doc/userprog.texi
b/doc/userprog.texi
index 67d7853bc94ee4da9910fce62bf3d90832e0abaf..903d9c53311dcd856860b10a5749ffdbd234d3ab 100644
(file)
--- a/
doc/userprog.texi
+++ b/
doc/userprog.texi
@@
-476,7
+476,7
@@
because there's no way to return an error code from a memory access.
Therefore, for those who want to try the latter technique, we'll
provide a little bit of helpful code:
Therefore, for those who want to try the latter technique, we'll
provide a little bit of helpful code:
-@
example
+@
verbatim
/* Tries to copy a byte from user address USRC to kernel address DST.
Returns true if successful, false if USRC is invalid. */
static inline bool get_user (uint8_t *dst, const uint8_t *usrc) {
/* Tries to copy a byte from user address USRC to kernel address DST.
Returns true if successful, false if USRC is invalid. */
static inline bool get_user (uint8_t *dst, const uint8_t *usrc) {
@@
-494,7
+494,7
@@
static inline bool put_user (uint8_t *udst, uint8_t byte) {
: "=m" (*udst), "=&a" (eax) : "r" (byte));
return eax != 0;
}
: "=m" (*udst), "=&a" (eax) : "r" (byte));
return eax != 0;
}
-@end
example
+@end
verbatim
Each of these functions assumes that the user address has already been
verified to be below @code{PHYS_BASE}. They also assume that you've
Each of these functions assumes that the user address has already been
verified to be below @code{PHYS_BASE}. They also assume that you've
@@
-805,12
+805,12
@@
You may find the non-standard @func{hex_dump} function, declared in
Here's what it would show in the above example, given that
@code{PHYS_BASE} is @t{0xc0000000}:
Here's what it would show in the above example, given that
@code{PHYS_BASE} is @t{0xc0000000}:
-@
example
+@
verbatim
bfffffc0 00 00 00 00 | ....|
bfffffd0 04 00 00 00 d8 ff ff bf-ed ff ff bf f5 ff ff bf |................|
bfffffe0 f8 ff ff bf fc ff ff bf-00 00 00 00 00 2f 62 69 |............./bi|
bffffff0 6e 2f 6c 73 00 2d 6c 00-2a 2e 68 00 2a 2e 63 00 |n/ls.-l.*.h.*.c.|
bfffffc0 00 00 00 00 | ....|
bfffffd0 04 00 00 00 d8 ff ff bf-ed ff ff bf f5 ff ff bf |................|
bfffffe0 f8 ff ff bf fc ff ff bf-00 00 00 00 00 2f 62 69 |............./bi|
bffffff0 6e 2f 6c 73 00 2d 6c 00-2a 2e 68 00 2a 2e 63 00 |n/ls.-l.*.h.*.c.|
-@end
example
+@end
verbatim
@node System Calls
@section System Calls
@node System Calls
@section System Calls
@@
-850,7
+850,7
@@
arbitrary:
@html
<CENTER>
@end html
@html
<CENTER>
@end html
-@multitable {
Address
} {Value}
+@multitable {
@t{0xbffffe7c}
} {Value}
@item Address @tab Value
@item @t{0xbffffe7c} @tab 3
@item @t{0xbffffe78} @tab 2
@item Address @tab Value
@item @t{0xbffffe7c} @tab 3
@item @t{0xbffffe78} @tab 2