1. 21 8月, 2009 1 次提交
  2. 20 8月, 2009 1 次提交
  3. 13 8月, 2009 1 次提交
  4. 14 7月, 2009 1 次提交
    • M
      sh: Restore previous behaviour on kernel fault · 05dd2cd3
      Matt Fleming 提交于
      The last commit changed the behaviour on kernel faults when we were
      doing something other than syncing the page tables. vmalloc_sync_one()
      needs to return NULL if the page tables are up to date, because the
      reason for the fault was not a missing/inconsitent page table entry. By
      returning NULL if the page tables are sync'd we signal to the calling
      function that further work must be done to resolve this fault.
      
      Also, remove the superfluous __va() around the first argument to
      vmalloc_sync_one(). The value of pgd_k is already a virtual address and
      using it wth __va() causes a NULL dereference.
      Signed-off-by: NMatt Fleming <matt@console-pimps.org>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      05dd2cd3
  5. 13 7月, 2009 1 次提交
  6. 05 7月, 2009 2 次提交
  7. 04 7月, 2009 1 次提交
  8. 25 6月, 2009 2 次提交
  9. 23 6月, 2009 2 次提交
  10. 22 6月, 2009 1 次提交
  11. 18 6月, 2009 1 次提交
  12. 22 5月, 2009 1 次提交
  13. 14 5月, 2009 1 次提交
  14. 10 5月, 2009 1 次提交
  15. 09 5月, 2009 1 次提交
  16. 07 5月, 2009 2 次提交
  17. 20 4月, 2009 1 次提交
  18. 16 4月, 2009 1 次提交
  19. 14 4月, 2009 1 次提交
  20. 10 4月, 2009 1 次提交
  21. 02 4月, 2009 1 次提交
    • P
      sh: Kill off broken direct-mapped cache mode. · e8208828
      Paul Mundt 提交于
      Forcing direct-mapped worked on certain older 2-way set associative
      parts, but was always error prone on 4-way parts. As these are the
      norm these days, there is not much point in continuing to support this
      mode. Most of the folks that used direct-mapped mode generally just
      wanted writethrough caching in the first place..
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      e8208828
  22. 17 3月, 2009 3 次提交
  23. 16 3月, 2009 1 次提交
  24. 10 3月, 2009 1 次提交
  25. 27 2月, 2009 1 次提交
  26. 21 1月, 2009 1 次提交
  27. 07 1月, 2009 1 次提交
    • G
      mm: show node to memory section relationship with symlinks in sysfs · c04fc586
      Gary Hade 提交于
      Show node to memory section relationship with symlinks in sysfs
      
      Add /sys/devices/system/node/nodeX/memoryY symlinks for all
      the memory sections located on nodeX.  For example:
      /sys/devices/system/node/node1/memory135 -> ../../memory/memory135
      indicates that memory section 135 resides on node1.
      
      Also revises documentation to cover this change as well as updating
      Documentation/ABI/testing/sysfs-devices-memory to include descriptions
      of memory hotremove files 'phys_device', 'phys_index', and 'state'
      that were previously not described there.
      
      In addition to it always being a good policy to provide users with
      the maximum possible amount of physical location information for
      resources that can be hot-added and/or hot-removed, the following
      are some (but likely not all) of the user benefits provided by
      this change.
      Immediate:
        - Provides information needed to determine the specific node
          on which a defective DIMM is located.  This will reduce system
          downtime when the node or defective DIMM is swapped out.
        - Prevents unintended onlining of a memory section that was
          previously offlined due to a defective DIMM.  This could happen
          during node hot-add when the user or node hot-add assist script
          onlines _all_ offlined sections due to user or script inability
          to identify the specific memory sections located on the hot-added
          node.  The consequences of reintroducing the defective memory
          could be ugly.
        - Provides information needed to vary the amount and distribution
          of memory on specific nodes for testing or debugging purposes.
      Future:
        - Will provide information needed to identify the memory
          sections that need to be offlined prior to physical removal
          of a specific node.
      
      Symlink creation during boot was tested on 2-node x86_64, 2-node
      ppc64, and 2-node ia64 systems.  Symlink creation during physical
      memory hot-add tested on a 2-node x86_64 system.
      Signed-off-by: NGary Hade <garyhade@us.ibm.com>
      Signed-off-by: NBadari Pulavarty <pbadari@us.ibm.com>
      Acked-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      c04fc586
  28. 22 12月, 2008 6 次提交
  29. 13 11月, 2008 1 次提交