1. 10 5月, 2010 2 次提交
  2. 08 12月, 2009 1 次提交
  3. 21 9月, 2009 1 次提交
  4. 01 7月, 2009 1 次提交
  5. 19 6月, 2009 1 次提交
  6. 10 6月, 2009 1 次提交
  7. 14 4月, 2009 1 次提交
  8. 03 4月, 2009 2 次提交
  9. 24 8月, 2008 1 次提交
  10. 06 5月, 2008 1 次提交
  11. 08 2月, 2008 1 次提交
  12. 20 10月, 2007 1 次提交
  13. 12 9月, 2007 1 次提交
  14. 20 7月, 2007 22 次提交
  15. 13 2月, 2007 2 次提交
    • 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
  16. 06 8月, 2006 1 次提交
    • A
      [PATCH] drivers/edac/edac_mc.h must #include <linux/platform_device.h> · 927cbe8a
      Adrian Bunk 提交于
      With CONFIG_PCI=n:
      
        CC      drivers/edac/edac_mc.o
      drivers/edac/edac_mc.c: In function ‘add_mc_to_global_list’:
      drivers/edac/edac_mc.c:1362: error: implicit declaration of function ‘to_platform_device’
      drivers/edac/edac_mc.c:1362: error: invalid type argument of ‘->’
      drivers/edac/edac_mc.c: In function ‘edac_mc_add_mc’:
      drivers/edac/edac_mc.c:1467: error: invalid type argument of ‘->’
      drivers/edac/edac_mc.c: In function ‘edac_mc_del_mc’:
      drivers/edac/edac_mc.c:1504: error: invalid type argument of ‘->’
      Signed-off-by: NAdrian Bunk <bunk@stusta.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      927cbe8a