nits in index.txt
add slides for shell, x86 intro, x86 virtual memory (deleted JOS from slides)
This commit is contained in:
parent
f53494c28e
commit
e87dca5cc5
9 changed files with 19 additions and 13 deletions
|
@ -1,3 +1,3 @@
|
||||||
index.html: index.txt mkhtml
|
index.html: index.txt mkhtml
|
||||||
mkhtml index.txt >_$@ && mv _$@ $@
|
./mkhtml index.txt >_$@ && mv _$@ $@
|
||||||
|
|
||||||
|
|
|
@ -70,11 +70,10 @@ Intel x86 machines.
|
||||||
Xv6's use of the x86 makes it more relevant to
|
Xv6's use of the x86 makes it more relevant to
|
||||||
students' experience than V6 was
|
students' experience than V6 was
|
||||||
and unifies the course around a single architecture.
|
and unifies the course around a single architecture.
|
||||||
Adding multiprocessor support also helps relevance
|
Adding multiprocessor support requires handling concurrency head on with
|
||||||
and makes it easier to discuss threads and concurrency.
|
locks and threads (instead of using special-case solutions for
|
||||||
(In a single processor operating system, concurrency–which only
|
uniprocessors such as
|
||||||
happens because of interrupts–is too easy to view as a special case.
|
enabling/disabling interrupts) and helps relevance.
|
||||||
A multiprocessor operating system must attack the problem head on.)
|
|
||||||
Finally, writing a new system allowed us to write cleaner versions
|
Finally, writing a new system allowed us to write cleaner versions
|
||||||
of the rougher parts of V6, like the scheduler and file system.
|
of the rougher parts of V6, like the scheduler and file system.
|
||||||
<br><br>
|
<br><br>
|
||||||
|
@ -85,7 +84,8 @@ Since then, xv6 has stabilized, so we are making it
|
||||||
available in the hopes that others will find it useful too.
|
available in the hopes that others will find it useful too.
|
||||||
<br><br>
|
<br><br>
|
||||||
6.828 uses both xv6 and Jos.
|
6.828 uses both xv6 and Jos.
|
||||||
Courses taught at UCLA, NYU, and Stanford have used
|
Courses taught at UCLA, NYU, Peking University, Stanford, Tsinghua,
|
||||||
|
and University Texas (Austin) have used
|
||||||
Jos without xv6; we believe other courses could use
|
Jos without xv6; we believe other courses could use
|
||||||
xv6 without Jos, though we are not aware of any that have.
|
xv6 without Jos, though we are not aware of any that have.
|
||||||
|
|
||||||
|
@ -130,6 +130,7 @@ Jos labs, students implement a Unix-like interface
|
||||||
and culminating in a Unix shell.
|
and culminating in a Unix shell.
|
||||||
<br><br>
|
<br><br>
|
||||||
<a href="l1.html">lecture notes</a>
|
<a href="l1.html">lecture notes</a>
|
||||||
|
<a href="os-lab-1.pdf">OS abstractions slides</a>
|
||||||
|
|
||||||
<br><br><b><i>Lecture 2. PC hardware and x86 programming</i></b>
|
<br><br><b><i>Lecture 2. PC hardware and x86 programming</i></b>
|
||||||
<br><br>
|
<br><br>
|
||||||
|
@ -143,6 +144,7 @@ Reading: PC Assembly Language
|
||||||
Homework: familiarize with Bochs
|
Homework: familiarize with Bochs
|
||||||
<br><br>
|
<br><br>
|
||||||
<a href="l2.html">lecture notes</a>
|
<a href="l2.html">lecture notes</a>
|
||||||
|
<a href="os-lab-2.pdf">x86 intro slides</a>
|
||||||
<a href="x86-intro.html">homework</a>
|
<a href="x86-intro.html">homework</a>
|
||||||
|
|
||||||
<br><br><b><i>Lecture 3. Operating system organization</i></b>
|
<br><br><b><i>Lecture 3. Operating system organization</i></b>
|
||||||
|
@ -180,6 +182,7 @@ xv6: bootasm.S, bootother.S, <a href="src/bootmain.c.html">bootmain.c</a>, <a hr
|
||||||
Homework: Bochs stack introduction
|
Homework: Bochs stack introduction
|
||||||
<br><br>
|
<br><br>
|
||||||
<a href="l4.html">lecture notes</a>
|
<a href="l4.html">lecture notes</a>
|
||||||
|
<a href="os-lab-3.pdf">x86 virtual memory slides</a>
|
||||||
<a href="xv6-intro.html">homework</a>
|
<a href="xv6-intro.html">homework</a>
|
||||||
|
|
||||||
<br><br><b><i>Lecture 5. Address spaces using page tables</i></b>
|
<br><br><b><i>Lecture 5. Address spaces using page tables</i></b>
|
||||||
|
|
|
@ -36,11 +36,10 @@ Intel x86 machines.
|
||||||
Xv6's use of the x86 makes it more relevant to
|
Xv6's use of the x86 makes it more relevant to
|
||||||
students' experience than V6 was
|
students' experience than V6 was
|
||||||
and unifies the course around a single architecture.
|
and unifies the course around a single architecture.
|
||||||
Adding multiprocessor support also helps relevance
|
Adding multiprocessor support requires handling concurrency head on with
|
||||||
and makes it easier to discuss threads and concurrency.
|
locks and threads (instead of using special-case solutions for
|
||||||
(In a single processor operating system, concurrency--which only
|
uniprocessors such as
|
||||||
happens because of interrupts--is too easy to view as a special case.
|
enabling/disabling interrupts) and helps relevance.
|
||||||
A multiprocessor operating system must attack the problem head on.)
|
|
||||||
Finally, writing a new system allowed us to write cleaner versions
|
Finally, writing a new system allowed us to write cleaner versions
|
||||||
of the rougher parts of V6, like the scheduler and file system.
|
of the rougher parts of V6, like the scheduler and file system.
|
||||||
|
|
||||||
|
@ -51,7 +50,8 @@ Since then, xv6 has stabilized, so we are making it
|
||||||
available in the hopes that others will find it useful too.
|
available in the hopes that others will find it useful too.
|
||||||
|
|
||||||
6.828 uses both xv6 and Jos.
|
6.828 uses both xv6 and Jos.
|
||||||
Courses taught at UCLA, NYU, and Stanford have used
|
Courses taught at UCLA, NYU, Peking University, Stanford, Tsinghua,
|
||||||
|
and University Texas (Austin) have used
|
||||||
Jos without xv6; we believe other courses could use
|
Jos without xv6; we believe other courses could use
|
||||||
xv6 without Jos, though we are not aware of any that have.
|
xv6 without Jos, though we are not aware of any that have.
|
||||||
|
|
||||||
|
@ -101,6 +101,7 @@ Jos labs, students implement a Unix-like interface
|
||||||
and culminating in a Unix shell.
|
and culminating in a Unix shell.
|
||||||
|
|
||||||
[l1.html | lecture notes]
|
[l1.html | lecture notes]
|
||||||
|
[os-lab-1.pdf | OS abstractions slides]
|
||||||
|
|
||||||
|
|
||||||
Lecture 2. PC hardware and x86 programming
|
Lecture 2. PC hardware and x86 programming
|
||||||
|
@ -115,6 +116,7 @@ Reading: PC Assembly Language
|
||||||
Homework: familiarize with Bochs
|
Homework: familiarize with Bochs
|
||||||
|
|
||||||
[l2.html | lecture notes]
|
[l2.html | lecture notes]
|
||||||
|
[os-lab-2.pdf | x86 intro slides]
|
||||||
[x86-intro.html | homework]
|
[x86-intro.html | homework]
|
||||||
|
|
||||||
|
|
||||||
|
@ -154,6 +156,7 @@ xv6: bootasm.S, bootother.S, bootmain.c, main.c, init.c, and setupsegs in proc.c
|
||||||
Homework: Bochs stack introduction
|
Homework: Bochs stack introduction
|
||||||
|
|
||||||
[l4.html | lecture notes]
|
[l4.html | lecture notes]
|
||||||
|
[os-lab-3.pdf | x86 virtual memory slides]
|
||||||
[xv6-intro.html | homework]
|
[xv6-intro.html | homework]
|
||||||
|
|
||||||
|
|
||||||
|
|
BIN
web/os-lab-1.pdf
Normal file
BIN
web/os-lab-1.pdf
Normal file
Binary file not shown.
BIN
web/os-lab-1.ppt
Normal file
BIN
web/os-lab-1.ppt
Normal file
Binary file not shown.
BIN
web/os-lab-2.pdf
Normal file
BIN
web/os-lab-2.pdf
Normal file
Binary file not shown.
BIN
web/os-lab-2.ppt
Normal file
BIN
web/os-lab-2.ppt
Normal file
Binary file not shown.
BIN
web/os-lab-3.pdf
Normal file
BIN
web/os-lab-3.pdf
Normal file
Binary file not shown.
BIN
web/os-lab-3.ppt
Normal file
BIN
web/os-lab-3.ppt
Normal file
Binary file not shown.
Loading…
Reference in a new issue