1. 20 7月, 2007 33 次提交
  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. 17 7月, 2007 1 次提交
  4. 10 5月, 2007 1 次提交
  5. 09 5月, 2007 1 次提交
    • J
      Fix 82875 PCI setup · 62456726
      John Feeney 提交于
      The 82875 EDAC driver enables an otherwise-hidden PCI device, but doesn't
      register it as a PCI device properly.  Therefore, the device list in
      /proc/bus/pci/devices is different than the tree in /sys/bus/pci.  This
      usually manifests as the X server failing to start, since it expects the
      two lists to be consistent.
      Signed-off-by: NAdam Jackson <ajackson@redhat.com>
      Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
      Cc: Greg KH <greg@kroah.com>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Cc: Doug Thompson <norsk5@xmission.com>
      Cc: Andi Kleen <ak@suse.de>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      62456726
  6. 13 2月, 2007 3 次提交
    • E
      [PATCH] EDAC: Add Fully-Buffered DIMM APIs to core · 9794f33d
      eric wollesen 提交于
      Eric Wollesen ported the Bluesmoke Memory Controller driver for the Intel
      5000X/V/P (Blackford/Greencreek) chipset to the in kernel EDAC model.
      
      This patch incorporates those required changes to the edac_mc.c and edac_mc.h
      core files by added new Fully Buffered DIMM interface to the EDAC Core module.
      Signed-off-by: Neric wollesen <ericw@xmtp.net>
      Signed-off-by: Ndoug thompson <norsk5@xmission.com>
      Acked-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      9794f33d
    • F
      [PATCH] EDAC: Add memory scrubbing controls API to core · 4f423ddf
      Frithiof Jensen 提交于
      This is an attempt of providing an interface for memory scrubbing control in
      EDAC.
      
      This patch modifies the EDAC Core to provide the Interface for memory
      controller modules to implment.
      
      The following things are still outstanding:
      
       - K8 is the first implemenation,
      
         The patch provide a method of configuring the K8 hardware memory scrubber
         via the 'mcX' sysfs directory.  There should be some fallback to a generic
         scrubber implemented in software if the hardware does not support
         scrubbing.
      
         Or .. the scrubbing sysfs entry should not be visible at all.
      
       - Only works with SDRAM, not cache,
      
         The K8 can scrub cache and l2cache also - but I think this is not so
         useful as the cache is busy all the time (one hopes).
      
         One would also expect that cache scrubbing requires hardware support.
      
       - Error Handling,
      
         I would like that errors are returned to the user in "terms of file
         system".
      
       - Presentation,
      
         I chose Bandwidth in Bytes/Second as a representation of the scrubbing
         rate for the following reasons:
      
         I like that the sysfs entries are sort-of textual, related to something
         that makes sense instead of magical values that must be looked up.
      
         "My People" wants "% main memory scrubbed per hour" others prefer "%
         memory bandwidth used" as representation, "bandwith used" makes it easy to
         calculate both versions in one-liner scripts.
      
         If one later wants to scrub cache, the scaling becomes wierd for K8
         changing from "blocks of 64 byte memory" to "blocks of 64 cache lines" to
         "blocks of 64 bit".  Using "bandwidth used" makes sense in all three cases,
         (I.M.O.  anyway ;-).
      
       - Discovery,
      
         There is no way to discover the possible settings and what they do
         without reading the code and the documentation.
      
         *I* do not know how to make that work in a practical way.
      
       - Bugs(??),
      
         other tools can set invalid values in the memory scrub control register,
         those will read back as '-1', requiring the user to reset the scrub rate.
         This is how *I* think it should be.
      
       - Afflicting other areas of code,
      
         I made changes to edac_mc.c and edac_mc.h which will show up globally -
         this is not nice, it would be better that the memory scrubbing fuctionality
         and interface could be entirely contained within the memory controller it
         applies to.
      
      Frithiof Jensen
      
      edac_mc.c and its .h file is a CORE helper module for EDAC
      driver modules. This provides the abstraction for device specific
      drivers. It is fine to modify this CORE to provide help for
      new features of the the drivers
      
      doug thompson
      Signed-off-by: NFrithiof Jensen <frithiof.jensen@ericson.com>
      Signed-off-by: Ndoug thompson <norsk5@xmission.com>
      Acked-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      4f423ddf
    • M
      [PATCH] EDAC: Fix in e752x mc driver · 84db003f
      Mike Chan 提交于
      This fix/change returns the offset into the page for the ce/ue error, instead
      of just 0.  The e752x dram controller reads 34:6 of the linear address with
      the error.
      Signed-off-by: NMike Chan <mikechan@google.com>
      Signed-off-by: Ndoug thompson <norsk5@xmission.com>
      Acked-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      84db003f