History log of /xv6-public/swtch.S (Results 1 – 10 of 10)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: xv6-rev11
# 6710e558 30-Aug-2018 Frans Kaashoek <kaashoek@mit.edu>

thanks wxdao


# 1ab23170 08-Oct-2017 Robert Morris <rtm@csail.mit.edu>

improve swtch comment


Revision tags: xv6-rev9, xv6-rev8, xv6-rev7, osdi12-submit, xv6-rev6, xv6-rev5, xv6-2010, xv6-rev4
# 2cf6b32d 05-Aug-2010 Robert Morris <rtm@nephron.lcs.mit.edu>

move jkstack to main.c
replace jstack with asm()s


# 40889627 02-Jul-2010 Frans Kaashoek <kaashoek@fransk-6.local>

Initial version of single-cpu xv6 with page tables


Revision tags: xv6-rev3
# 2c5f7aba 12-Jul-2009 Russ Cox <rsc@swtch.com>

initproc, usegment, swtch tweaks


# c100d9ee 15-Oct-2008 kolya <kolya>

cleaner swtch.S


Revision tags: xv6-2008
# c95bde81 27-Sep-2007 rsc <rsc>

yank out stack overflow checking ugliness


# 39c3fb1b 27-Sep-2007 rsc <rsc>

overkill: use segments to catch stack overflow (delete before next year)


Revision tags: xv6-2007, xv6-rev1
# 818fc012 28-Aug-2007 rsc <rsc>

replace setjmp/longjmp with swtch


Revision tags: symlinks, xv6-2006, xv6-rev0
# 5ce9751c 11-Jul-2006 rsc <rsc>

Changes to allow use of native x86 ELF compilers, which on my
Linux 2.4 box using gcc 3.4.6 don't seem to follow the same
conventions as the i386-jos-elf-gcc compilers.
Can run make 'TOOLPREFIX=' or

Changes to allow use of native x86 ELF compilers, which on my
Linux 2.4 box using gcc 3.4.6 don't seem to follow the same
conventions as the i386-jos-elf-gcc compilers.
Can run make 'TOOLPREFIX=' or edit the Makefile.

curproc[cpu()] can now be NULL, indicating that no proc is running.
This seemed safer to me than having curproc[0] and curproc[1]
both pointing at proc[0] potentially.

The old implementation of swtch depended on the stack frame layout
used inside swtch being okay to return from on the other stack
(exactly the V6 you are not expected to understand this).
It also could be called in two contexts: at boot time, to schedule
the very first process, and later, on behalf of a process, to sleep
or schedule some other process.

I split this into two functions: scheduler and swtch.

The scheduler is now a separate never-returning function, invoked
by each cpu once set up. The scheduler looks like:

scheduler() {
setjmp(cpu.context);

pick proc to schedule
blah blah blah

longjmp(proc.context)
}

The new swtch is intended to be called only when curproc[cpu()] is not NULL,
that is, only on behalf of a user proc. It does:

swtch() {
if(setjmp(proc.context) == 0)
longjmp(cpu.context)
}

to save the current proc context and then jump over to the scheduler,
running on the cpu stack.

Similarly the system call stubs are now in assembly in usys.S to avoid
needing to know the details of stack frame layout used by the compiler.

Also various changes in the debugging prints.

show more ...