1. 07 Mar, 2003 5 commits
    • Ingo Molnar's avatar
      [PATCH] "interactivity changes", sched-2.5.64-B2 · 23850f8d
      Ingo Molnar authored
      This fixes the SMP runqueue locking bug when updating the wakers
      priority.  It also includes:
      
       - only update the priority and do a requeueing if the sleep average has
         changed. (this does not happen for pure CPU hogs or pure interactive
         tasks, so no need to requeue/recalc-prio in that case.) [All the
         necessary values are available at that point already, so gcc should
         have an easy job making this branch really cheap.]
      
       - do not do a full task activation in the migration-thread path - that is
         supposed to be near-atomic anyway.
      
       - fix up comments
      
      I solved the SMP locking bug by moving the requeueing outside of
      try_to_wake_up().  It does not matter that the priority update is not
      atomically done now, since the current process wont do anything
      inbetween.  (well, it could get preempted in a preemptible kernel, but
      even that wont do any harm.)
      23850f8d
    • Stephen Hemminger's avatar
      [PATCH] Turn off aio printk meant for debugging (2.5.64) · 3ec83948
      Stephen Hemminger authored
      The following messages are of interest only when debugging aio.
      Otherwise, they are just console clutter.
      3ec83948
    • Matthew Wilcox's avatar
      [PATCH] fs/locks.c: fix bugs · 9df53b3b
      Matthew Wilcox authored
      - Remove broken lock accounting
      - Introduce __locks_delete_block()
      - Stop using kdevname()
      - Fix locks_remove_posix()
      9df53b3b
    • Ingo Molnar's avatar
      [PATCH] more "interactivity changes", sched-B2 · 74c72d80
      Ingo Molnar authored
       - fix a (now-) bug in kernel/softirq.c, it did a wakeup outside any
         atomic regions, which falsely identified random processes as a
         non-atomic wakeup, and which causes random priority boost to be
         distributed.
      
       - reset the initial idle thread's priority back to PRIO_MAX after doing
         the wakeup_forked_process() - correct preemption relies on this.
      
       - update current->prio immediately after a backboost.
      
       - clean up effective_prio() & sleep_avg calculations so that there are
         fewer RT-task special cases.  This has the advantage of the sleep_avg
         being maintained even for RT tasks - this could be advantegous for
         tasks that briefly enter/exit RT mode.
      74c72d80
    • Oleg Drokin's avatar
      [PATCH] memleak in drivers/char/vt.c · 5667cc2b
      Oleg Drokin authored
      Seems there is a memleak on error exit path in drivers/char/vt.c, here's
      the patch.  Found with help of smatch + enhanced unfree script.
      5667cc2b
  2. 06 Mar, 2003 35 commits