1. 10 10月, 2007 3 次提交
  2. 18 7月, 2007 1 次提交
    • R
      Freezer: make kernel threads nonfreezable by default · 83144186
      Rafael J. Wysocki 提交于
      Currently, the freezer treats all tasks as freezable, except for the kernel
      threads that explicitly set the PF_NOFREEZE flag for themselves.  This
      approach is problematic, since it requires every kernel thread to either
      set PF_NOFREEZE explicitly, or call try_to_freeze(), even if it doesn't
      care for the freezing of tasks at all.
      
      It seems better to only require the kernel threads that want to or need to
      be frozen to use some freezer-related code and to remove any
      freezer-related code from the other (nonfreezable) kernel threads, which is
      done in this patch.
      
      The patch causes all kernel threads to be nonfreezable by default (ie.  to
      have PF_NOFREEZE set by default) and introduces the set_freezable()
      function that should be called by the freezable kernel threads in order to
      unset PF_NOFREEZE.  It also makes all of the currently freezable kernel
      threads call set_freezable(), so it shouldn't cause any (intentional)
      change of behaviour to appear.  Additionally, it updates documentation to
      describe the freezing of tasks more accurately.
      
      [akpm@linux-foundation.org: build fixes]
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Acked-by: NNigel Cunningham <nigel@nigel.suspend2.net>
      Cc: Pavel Machek <pavel@ucw.cz>
      Cc: Oleg Nesterov <oleg@tv-sign.ru>
      Cc: Gautham R Shenoy <ego@in.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      83144186
  3. 28 4月, 2007 2 次提交
  4. 21 2月, 2007 2 次提交
  5. 18 2月, 2007 1 次提交
  6. 08 12月, 2006 1 次提交
  7. 26 11月, 2006 1 次提交
  8. 04 10月, 2006 1 次提交
  9. 26 9月, 2006 4 次提交
  10. 30 7月, 2006 1 次提交
  11. 01 7月, 2006 2 次提交
  12. 26 6月, 2006 2 次提交
  13. 25 6月, 2006 5 次提交
  14. 13 5月, 2006 1 次提交
  15. 02 4月, 2006 1 次提交
    • A
      V4L/DVB (3673): Fix budget-av CAM reset · 86f40cc3
      Andrew de Quincey 提交于
      Unfortunately on the budget-av board, the CAM reset line is tied to the
      frontend reset line, so resetting the CAM also zaps the frontend. This
      breaks the tda1004x at least, and causes it to fail to tune until the
      budget-av module is reloaded. This patch adds an exported function to dvb_frontend
      that allows a card to forcibly reinitialise a frontend. The budget-av now
      does this on CAM reset, which corrects this problem.
      since they do not tie the CAM reset line to the frontend reset line.
      Signed-off-by: NAndrew de Quincey <adq_dvb@lidskialf.net>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@infradead.org>
      86f40cc3
  16. 27 2月, 2006 1 次提交
  17. 07 2月, 2006 1 次提交
  18. 12 1月, 2006 1 次提交
  19. 10 1月, 2006 3 次提交
  20. 13 12月, 2005 1 次提交
  21. 09 11月, 2005 2 次提交
  22. 08 7月, 2005 2 次提交
  23. 26 6月, 2005 1 次提交
    • C
      [PATCH] Cleanup patch for process freezing · 3e1d1d28
      Christoph Lameter 提交于
      1. Establish a simple API for process freezing defined in linux/include/sched.h:
      
         frozen(process)		Check for frozen process
         freezing(process)		Check if a process is being frozen
         freeze(process)		Tell a process to freeze (go to refrigerator)
         thaw_process(process)	Restart process
         frozen_process(process)	Process is frozen now
      
      2. Remove all references to PF_FREEZE and PF_FROZEN from all
         kernel sources except sched.h
      
      3. Fix numerous locations where try_to_freeze is manually done by a driver
      
      4. Remove the argument that is no longer necessary from two function calls.
      
      5. Some whitespace cleanup
      
      6. Clear potential race in refrigerator (provides an open window of PF_FREEZE
         cleared before setting PF_FROZEN, recalc_sigpending does not check
         PF_FROZEN).
      
      This patch does not address the problem of freeze_processes() violating the rule
      that a task may only modify its own flags by setting PF_FREEZE. This is not clean
      in an SMP environment. freeze(process) is therefore not SMP safe!
      Signed-off-by: NChristoph Lameter <christoph@lameter.com>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      3e1d1d28