From b5f0874cd96ee2a62aabc645b9626c2749cb6a01 Mon Sep 17 00:00:00 2001 From: manuel Date: Mon, 26 Mar 2012 12:54:45 +0200 Subject: initial pintos checkin --- doc/pintos_fot.html | 79 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 79 insertions(+) create mode 100644 doc/pintos_fot.html (limited to 'doc/pintos_fot.html') diff --git a/doc/pintos_fot.html b/doc/pintos_fot.html new file mode 100644 index 0000000..820500e --- /dev/null +++ b/doc/pintos_fot.html @@ -0,0 +1,79 @@ + + + + + +Pintos Projects: Footnotes + + + + + + + + + + + + + + + + + +

[Top]

[Index]

[ ? ]

Footnotes

(1)

GDB might tell you that +schedule() doesn't exist, which is arguably a GDB bug. +You can work around this by setting the breakpoint by filename and +line number, e.g. break thread.c:ln where ln is +the line number of the first declaration in schedule(). +

(2)

We +will treat these terms as synonyms. There is no standard +distinction between them, although Intel processor manuals make +a minor distinction between them on 80x86. +

(3)

This is because switch_threads() takes +arguments on the stack and the 80x86 SVR4 calling convention +requires the caller, not the called function, to remove them when the +call is complete. See [ SysV-i386] chapter 3 for details. +

(4)

Actually, virtual to physical translation on the +80x86 architecture occurs via an intermediate "linear +address," but Pintos (and most modern 80x86 OSes) set up the CPU +so that linear and virtual addresses are one and the same. Thus, you +can effectively ignore this CPU feature. +

Footnotes

(1)

(2)

(3)

(4)

(5)

(6)

(7)