1. 23 Jun, 2009 2 commits
  2. 22 May, 2009 1 commit
  3. 06 Jan, 2009 1 commit
    • Gary Hade's avatar
      mm: show node to memory section relationship with symlinks in sysfs · c04fc586
      Gary Hade authored
      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.
        - 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.
        - 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: default avatarGary Hade <garyhade@us.ibm.com>
      Signed-off-by: default avatarBadari Pulavarty <pbadari@us.ibm.com>
      Acked-by: default avatarIngo Molnar <mingo@elte.hu>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  4. 10 Nov, 2008 1 commit
  5. 21 Oct, 2008 1 commit
  6. 20 Sep, 2008 1 commit
    • Paul Mundt's avatar
      sh: Support kernel stacks smaller than a page. · c15c5f8c
      Paul Mundt authored
      This follows the powerpc commit f6a61680
      '[POWERPC] Fix kernel stack allocation alignment'.
      SH has traditionally forced the thread order to be relative to the page
      size, so there were never any situations where the same bug was
      triggered by slub. Regardless, the usage of > 8kB stacks for the larger
      page sizes is overkill, so we switch to using slab allocations there,
      as per the powerpc change.
      Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
  7. 08 Sep, 2008 3 commits
  8. 26 Jul, 2008 1 commit
  9. 24 Jul, 2008 1 commit
  10. 28 Apr, 2008 1 commit
  11. 06 Mar, 2008 1 commit
  12. 14 Feb, 2008 1 commit
  13. 28 Jan, 2008 4 commits
  14. 16 Oct, 2007 1 commit
  15. 11 Jun, 2007 1 commit
  16. 08 Jun, 2007 4 commits
  17. 21 May, 2007 2 commits
  18. 09 May, 2007 1 commit
  19. 07 May, 2007 1 commit
  20. 13 Feb, 2007 2 commits
  21. 11 Feb, 2007 1 commit
  22. 11 Dec, 2006 1 commit
  23. 06 Dec, 2006 4 commits
    • Paul Mundt's avatar
      sh: Fixup various PAGE_SIZE == 4096 assumptions. · 510c72ad
      Paul Mundt authored
      There were a number of places that made evil PAGE_SIZE == 4k
      assumptions that ended up breaking when trying to play with
      8k and 64k page sizes, this fixes those up.
      The most significant change is the way we load THREAD_SIZE,
      previously this was done via:
      	mov	#(THREAD_SIZE >> 8), reg
      	shll8	reg
      to avoid a memory access and allow the immediate load. With
      a 64k PAGE_SIZE, we're out of range for the immediate load
      size without resorting to special instructions available in
      later ISAs (movi20s and so on). The "workaround" for this is
      to bump up the shift to 10 and insert a shll2, which gives a
      bit more flexibility while still being much cheaper than a
      memory access.
      Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
    • Stuart Menefy's avatar
      sh: pmd rework. · 99a596f9
      Stuart Menefy authored
      Remove extra bits from the pmd structure and store a kernel logical
      address rather than a physical address. This allows it to be directly
      dereferenced. Another piece of wierdness inherited from x86.
      Signed-off-by: default avatarStuart Menefy <stuart.menefy@st.com>
      Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
    • Stuart Menefy's avatar
      sh: Use MMU.TTB register as pointer to current pgd. · 6e4662ff
      Stuart Menefy authored
      Add TTB accessor functions and give it a sensible default
      value. We will use this later for optimizing the fault
      Signed-off-by: default avatarStuart Menefy <stuart.menefy@st.com>
      Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
    • Paul Mundt's avatar
      sh: Preliminary support for SH-X2 MMU. · 21440cf0
      Paul Mundt authored
      This adds some preliminary support for the SH-X2 MMU, used by
      newer SH-4A parts (particularly SH7785).
      This MMU implements a 'compat' mode with SH-X MMUs and an
      'extended' mode for SH-X2 extended features. Extended features
      include additional page sizes (8kB, 4MB, 64MB), as well as the
      addition of page execute permissions.
      The extended mode attributes are placed in a second data array,
      which requires us to switch to 64-bit PTEs when in X2 mode.
      With the addition of the exec perms, we also overhaul the mmap
      prots somewhat, now that it's possible to handle them more
      Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
  24. 27 Sep, 2006 3 commits