135e2/xv6-labs.git - xv6-labs-2024-winter

Age	Commit message (Collapse)	Author	Files	Lines
2006-09-07	one regression test program	kaashoek	1	-210/+0

2006-09-06	wrap long lines	rsc	1	-1/+2

2006-09-06	weird spacing	rsc	1	-4/+4

2006-09-06	standardize various * conventions	rsc	1	-27/+27

2006-09-06	spacing fixes: no tabs, 2-space indents (for rtm)	rsc	1	-2/+2

2006-09-03	nits	kaashoek	1	-1/+0

2006-08-24	fix bugs in indirect-file code	kaashoek	1	-25/+133
	clean up test program
2006-08-24	user-level malloc (untested)	kaashoek	1	-3/+3
	nit in sbrk indirect block fix dup to share fd struct
2006-08-23	i/o redirection in sh	kaashoek	1	-0/+4
	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?
2006-08-20	removed block system call	kaashoek	1	-2/+0
	renumber system calls (run gmake clean!) skeleton for dup system call
2006-08-14	user-level programs: mkdir and rm	kaashoek	1	-1/+1
	shell parses arguments (very simplistic) readme version of README (sh doesn't deal with capital characters) printf recognizes %c nicer output format for ls
2006-08-14	start on mkdir	kaashoek	1	-0/+13
	stat
2006-08-13	zero freed blocks	kaashoek	1	-0/+15
	multi-block directories track size of directory (size = number entries in use) should namei (and other code that scans through directories) scan through all blocks of a directory and not use size?
2006-08-12	fstat	kaashoek	1	-1/+2
	primitive ls
2006-08-12	unlink,mknod,create with multi-component pathnames should work now	kaashoek	1	-8/+2
	remove console init code from userfs
2006-08-11	fix deadlock---iput(dp) asap	kaashoek	1	-3/+4
	working unlink, but doesn't free dir blocks that become empty remove out-of-date comment in ioapic
2006-08-10	low-level keyboard input (not hooked up to /dev yet)	rtm	1	-0/+1
	fix acquire() to cli() before incrementing nlock make T_SYSCALL a trap gate, not an interrupt gate sadly, various crashes if you hold down a keyboard key...
2006-08-10	printf	kaashoek	1	-21/+37
	convert userfs to use printf bfree ifree writei start on unlink
2006-08-09	iread for T_DEV	kaashoek	1	-1/+9
	O_RDWR, etc. create file
2006-08-09	fix test program: don't close before writing	kaashoek	1	-1/+0
	set fd to writeable on open for write
2006-08-09	devsw	kaashoek	1	-0/+11
	checkpoint: write(fd,"hello\n",6) where fd is a console dev almost works
2006-08-08	fix race in holding() check in acquire()	rtm	1	-2/+4
	give cpu1 a TSS and gdt for when it enters scheduler() and a pseudo proc[] entry for each cpu cpu0 waits for each other cpu to start up read() for files
2006-08-08	mknod,ialloc,iupdate	kaashoek	1	-0/+8

2006-07-29	open()	rtm	1	-0/+16

2006-07-28	exec arguments	rtm	1	-1/+2

2006-07-27	primitive exec	rtm	1	-0/+1

2006-07-17	nitpicks	rsc	1	-1/+1

2006-07-16	Add user.h for prototypes.	rsc	1	-0/+4
	Add cons_puts for cleaner output.
2006-07-11	Changes to allow use of native x86 ELF compilers, which on my	rsc	1	-0/+1
	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.
2006-07-10	oops	kaashoek	1	-0/+8