Skip to content
Snippets Groups Projects
  1. Jan 11, 2011
    • Russ Cox's avatar
      make new code like old code · 1a81e38b
      Russ Cox authored
      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.
      1a81e38b
  2. Sep 13, 2010
  3. Sep 02, 2010
  4. Aug 31, 2010
  5. Aug 10, 2010
  6. Aug 06, 2010
  7. Aug 05, 2010
  8. Jul 25, 2010
  9. Jul 23, 2010
  10. Jul 02, 2010
  11. Sep 20, 2009
  12. Sep 03, 2009
  13. Sep 02, 2009
  14. Aug 30, 2009
    • Russ Cox's avatar
      assorted fixes: · 48755214
      Russ Cox authored
       * rename c/cp to cpu/proc
       * rename cpu.context to cpu.scheduler
       * fix some comments
       * formatting for printout
      48755214
  15. Aug 08, 2009
  16. Jul 12, 2009
  17. Jul 11, 2009
  18. May 30, 2009
    • rsc's avatar
      compile fixes · 27ff8f0e
      rsc authored
      27ff8f0e
    • rsc's avatar
      · 34295f46
      rsc authored
      group locks into structs they protect.
      few naming nits.
      34295f46
    • rsc's avatar
      clean up %fs %gs use · 7b644318
      rsc authored
      7b644318
    • rsc's avatar
      move fork into proc.c · 21573833
      rsc authored
      21573833
    • rsc's avatar
      · 19333efb
      rsc authored
      Some proc cleanup, moving some of copyproc into allocproc.
      
      Also, an experiment: use "thread-local" storage for c and cp
      instead of the #define macro for curproc[cpu()].
      19333efb
  19. Mar 08, 2009
  20. Oct 14, 2008
  21. Sep 11, 2008
  22. Aug 28, 2008
  23. Aug 27, 2008
  24. Oct 20, 2007
  25. Sep 27, 2007
    • rsc's avatar
      · ab08960f
      rsc authored
      Final word on the locking fiasco?
      
      Change pushcli / popcli so that they can never turn on
      interrupts unexpectedly.  That is, if interrupts are on,
      then pushcli(); popcli(); turns them off and back on, but
      if they are off to begin with, then pushcli(); popcli(); is
      a no-op.
      
      I think our fundamental mistake was having a primitive
      (release and then popcli nee spllo) that could turn
      interrupts on at unexpected moments instead of being
      explicit about when we want to start allowing interrupts.
      
      With the new semantics, all the manual fiddling of ncli
      to force interrupts off in certain sections goes away.
      In return, we must explicitly mark the places where
      we want to enable interrupts unconditionally, by calling sti().
      There is only one: inside the scheduler loop.
      ab08960f
    • rsc's avatar
      yank out stack overflow checking ugliness · c95bde81
      rsc authored
      c95bde81
    • rsc's avatar
      okay, that was long enough - revert · 4f74de0e
      rsc authored
      4f74de0e
Loading