1. 17 3月, 2009 1 次提交
    • P
      sh: Support for extended ASIDs on PTEAEX-capable SH-X3 cores. · 8263a67e
      Paul Mundt 提交于
      This adds support for extended ASIDs (up to 16-bits) on newer SH-X3 cores
      that implement the PTAEX register and respective functionality. Presently
      only the 65nm SH7786 (90nm only supports legacy 8-bit ASIDs).
      
      The main change is in how the PTE is written out when loading the entry
      in to the TLB, as well as in how the TLB entry is selectively flushed.
      
      While SH-X2 extended mode splits out the memory-mapped U and I-TLB data
      arrays for extra bits, extended ASID mode splits out the address arrays.
      While we don't use the memory-mapped data array access, the address
      array accesses are necessary for selective TLB flushes, so these are
      implemented newly and replace the generic SH-4 implementation.
      
      With this, TLB flushes in switch_mm() are almost non-existent on newer
      parts.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      8263a67e
  2. 16 3月, 2009 1 次提交
  3. 10 3月, 2009 1 次提交
  4. 27 2月, 2009 1 次提交
  5. 21 1月, 2009 1 次提交
  6. 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
  7. 22 12月, 2008 6 次提交
  8. 13 11月, 2008 1 次提交
  9. 12 11月, 2008 1 次提交
  10. 10 11月, 2008 1 次提交
  11. 31 10月, 2008 1 次提交
  12. 21 10月, 2008 1 次提交
  13. 20 10月, 2008 2 次提交
  14. 21 9月, 2008 3 次提交
    • P
      sh: Trivial trace_mark() instrumentation for core events. · 3d58695e
      Paul Mundt 提交于
      This implements a few trace points across events that are deemed
      interesting. This implements a number of trace points:
      
      	- The page fault handler / TLB miss
      	- IPC calls
      	- Kernel thread creation
      
      The original LTTng patch had the slow-path instrumented, which
      fails to account for the vast majority of events. In general
      placing this in the fast-path is not a huge performance hit, as
      we don't take page faults for kernel addresses.
      
      The other bits of interest are some of the other trap handlers, as
      well as the syscall entry/exit (which is better off being handled
      through the tracehook API). Most of the other trap handlers are corner
      cases where alternate means of notification exist, so there is little
      value in placing extra trace points in these locations.
      
      Based on top of the points provided both by the LTTng instrumentation
      patch as well as the patch shipping in the ST-Linux tree, albeit in a
      stripped down form.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      3d58695e
    • P
      sh: Kill off duplicate page fault notifiers in slow path. · 8f2baee2
      Paul Mundt 提交于
      We already have hooks in place in the __do_page_fault() fast-path,
      so kill them off in the slow path.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      8f2baee2
    • P
      887f1ae3
  15. 20 9月, 2008 1 次提交
    • P
      sh: Support kernel stacks smaller than a page. · c15c5f8c
      Paul Mundt 提交于
      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: NPaul Mundt <lethal@linux-sh.org>
      c15c5f8c
  16. 17 9月, 2008 1 次提交
  17. 08 9月, 2008 7 次提交
  18. 28 8月, 2008 1 次提交
  19. 11 8月, 2008 2 次提交
  20. 04 8月, 2008 2 次提交
  21. 29 7月, 2008 1 次提交
  22. 28 7月, 2008 3 次提交