summaryrefslogtreecommitdiff
path: root/console.c
AgeCommit message (Collapse)Author
2007-08-14fixesrsc
2007-08-14formatting; split kbd constants into kbd.hrsc
2007-08-10Make cp a magic symbol.rsc
2007-08-08check p->killed for long-lived sleepsrsc
2007-08-08missing voidrsc
2007-08-08add EOF handling to console_read - works with catrsc
2006-09-07debugging rearrangementsrsc
2006-09-07debugging printsrsc
2006-09-07fix ide, pit interfacesrsc
2006-09-07remove _ prefixesrsc
2006-09-07run without lapic and ioapic, if they are not presentkaashoek
if no lapic available, use 8253pit for clock now xv6 runs both on qemu (uniprocessor) and bochs (uniprocessor and MP)
2006-09-07nit in console interruptskaashoek
2006-09-06no /* */ commentsrsc
2006-09-06standardize various * conventionsrsc
2006-09-06spacing fixes: no tabs, 2-space indents (for rtm)rsc
2006-09-06print "0" for null stringrsc
2006-09-03don't send keyboard interrupts to the second cpu, if we have only one cpu.kaashoek
xv6 seems to work fine on uniprocessor now.
2006-09-03remove duplicationkaashoek
don't use the same name for two different pieces of code
2006-08-29clean up stale error checks and panicsrtm
delete unused functions a few comments
2006-08-23i/o redirection in shkaashoek
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-15commented out code for cwdkaashoek
2006-08-11init creates console, opens 0/1/2, runs shrtm
sh accepts 0-argument commands (like userfs) reads from console
2006-08-10interrupts could be recursive since lapic_eoi() called before rtirtm
so fast interrupts overflow the kernel stack fix: cli() before lapic_eoi()
2006-08-10low-level keyboard input (not hooked up to /dev yet)rtm
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-10printfkaashoek
convert userfs to use printf bfree ifree writei start on unlink
2006-08-09fix test program: don't close before writingkaashoek
set fd to writeable on open for write
2006-08-09devswkaashoek
checkpoint: write(fd,"hello\n",6) where fd is a console dev almost works
2006-07-29open()rtm
2006-07-20uint32_t -> uint &crtm
2006-07-17no more cons_putc; real_cons_putc -> cons_putcrsc
2006-07-17add uint and standardize on typedefs instead of unsignedrsc
2006-07-17nitpicksrsc
2006-07-16add %s to cprintf for cons_putsrsc
2006-07-16standardize on #include "foo" not <foo>rsc
2006-07-16remove non-idiomatic increment/decrementrsc
2006-07-16Attempt to clean up newproc somewhat.rsc
Also remove all calls to memcpy in favor of memmove, which has defined semantics when the ranges overlap. The fact that memcpy was working in console.c to scroll the screen is not guaranteed by all implementations.
2006-07-16New scheduler.rsc
Removed cli and sti stack in favor of tracking number of locks held on each CPU and explicit conditionals in spinlock.c.
2006-07-15no more recursive locksrtm
wakeup1() assumes you hold proc_table_lock sleep(chan, lock) provides atomic sleep-and-release to wait for condition ugly code in swtch/scheduler to implement new sleep fix lots of bugs in pipes, wait, and exit fix bugs if timer interrupt goes off in schedule() console locks per line, not per byte
2006-07-12i think my cmpxchg use was wrong in acquirertm
nesting cli/sti: release shouldn't always enable interrupts separate setup of lapic from starting of other cpus, so cpu() works earlier flag to disable locking in console output make locks work even when curproc==0 (still crashes in clock interrupt)
2006-07-12no more big kernel lockrtm
succeeds at usertests.c pipe test
2006-07-11Changes to allow use of native x86 ELF compilers, which on myrsc
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-06-22send console output to parallel portrtm
2006-06-12importrtm