1. 10 5月, 2010 3 次提交
  2. 04 12月, 2009 1 次提交
  3. 13 6月, 2009 1 次提交
  4. 27 7月, 2008 1 次提交
  5. 26 7月, 2008 1 次提交
  6. 08 2月, 2008 1 次提交
  7. 20 7月, 2007 1 次提交
  8. 13 2月, 2007 1 次提交
    • 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
  9. 11 7月, 2006 1 次提交
    • D
      [PATCH] Fix and enable EDAC sysfs operation · 49c0dab7
      Doug Thompson 提交于
      When EDAC was first introduced into the kernel it had a sysfs interface,
      but due to some problems it was disabled in 2.6.16 and remained disabled in
      2.6.17.
      
      With feedback, several of the control and attribute files of that interface
      had some good constructive feedback.  PCI Blacklist/Whitelist was a major
      set which has design issues and it has been removed in this patch.  Instead
      of storing PCI broken parity status in EDAC, it has been moved to the
      pci_dev structure itself by a previous PCI patch.  A future patch will
      enable that feature in EDAC by utilizing the pci_dev info.
      
      The sysfs is now enabled in this patch, with a minimal set of control and
      attribute files for examining EDAC state and for enabling/disabling the
      memory and PCI operations.
      
      The Documentation for EDAC has also been updated to reflect the new state
      of EDAC operation.
      Signed-off-by: NDoug Thompson <norsk5@xmisson.com>
      Cc: Greg KH <greg@kroah.com>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      49c0dab7
  10. 27 3月, 2006 1 次提交
  11. 19 1月, 2006 1 次提交