thanks tyfkda

Remove trailing white space with:
for f in *.{h,c}; do sed -i .sed 's/[[:blank:]]*$//' $f; done
(Thanks to Nicolás Wolovick)

make new code like old code

Variable declarations at top of function,
separate from initialization.

Use == 0 instead of ! for checking pointers.

Consistent spacing around {, *, casts.

Declare 0-p

make new code like old code

Variable declarations at top of function,
separate from initialization.

Use == 0 instead of ! for checking pointers.

Consistent spacing around {, *, casts.

Declare 0-parameter functions as (void) not ().

Integer valued functions return -1 on failure, 0 on success.

show more ...

xv6: use stosb for memset

Remove puts in favor of printf.
Allow multiple arguments to ls.

PDF at http://am.lcs.mit.edu/~rsc/xv6.pdf

Various changes made while offline.

+ bwrite sector argument is redundant; use b->sector.
+ reformatting of files for nicer PDF page breaks
+ distinguis

PDF at http://am.lcs.mit.edu/~rsc/xv6.pdf

Various changes made while offline.

+ bwrite sector argument is redundant; use b->sector.
+ reformatting of files for nicer PDF page breaks
+ distinguish between locked, unlocked inodes in type signatures
+ change FD_FILE to FD_INODE
+ move userinit (nee proc0init) to proc.c
+ move ROOTDEV to param.h
+ always parenthesize sizeof argument

show more ...

avoid assignments in declarations

standardize on not using unsigned keyword

atoi, for kill

change gets to return \n, to distinguish 0-byte read from empty line

break single-line if statements

standardize various * conventions

spacing fixes: no tabs, 2-space indents (for rtm)

i/o redirection in sh
better parsing of sh commands (copied from jos sh)
cat: read from 1 if no args
sbrk system call, but untested
getpid system call
moved locks in keyboard intr, but why do we get

i/o redirection in sh
better parsing of sh commands (copied from jos sh)
cat: read from 1 if no args
sbrk system call, but untested
getpid system call
moved locks in keyboard intr, but why do we get intr w. null characters from keyboard?

show more ...

set size for directories correctly in wdir and mkfs
mkdir
ls shows stat info for each dir entry

start on mkdir
stat

fix getblk to actually lock the block
no more cons_put system calls
usertests tests two processes writing files

init creates console, opens 0/1/2, runs sh
sh accepts 0-argument commands (like userfs)
reads from console

add %s to cprintf for cons_puts

Add user.h for prototypes.
Add cons_puts for cleaner output.

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 ...

disable all interrupts when acquiring lock
user program that makes a blocking system call

swtch saves callee-saved registers
swtch idles on per-CPU stack, not on calling process's stack
fix pipe bugs
usertest.c tests pipes, fork, exit, close

file descriptors
pipes