1. 23 Jun, 2009 2 commits
  2. 21 Jun, 2009 1 commit
  3. 18 Jun, 2009 1 commit
  4. 22 May, 2009 1 commit
  5. 14 May, 2009 1 commit
  6. 09 May, 2009 2 commits
  7. 07 May, 2009 2 commits
  8. 20 Apr, 2009 1 commit
  9. 16 Apr, 2009 1 commit
  10. 14 Apr, 2009 1 commit
  11. 09 Apr, 2009 1 commit
  12. 02 Apr, 2009 1 commit
    • Paul Mundt's avatar
      sh: Kill off broken direct-mapped cache mode. · e8208828
      Paul Mundt authored
      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: default avatarPaul Mundt <lethal@linux-sh.org>
  13. 17 Mar, 2009 3 commits
  14. 16 Mar, 2009 1 commit
  15. 10 Mar, 2009 1 commit
  16. 27 Feb, 2009 1 commit
  17. 21 Jan, 2009 1 commit
  18. 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>
  19. 22 Dec, 2008 6 commits
  20. 13 Nov, 2008 1 commit
  21. 12 Nov, 2008 1 commit
  22. 10 Nov, 2008 1 commit
  23. 31 Oct, 2008 1 commit
  24. 21 Oct, 2008 1 commit
  25. 20 Oct, 2008 2 commits
  26. 21 Sep, 2008 3 commits
    • Paul Mundt's avatar
      sh: Trivial trace_mark() instrumentation for core events. · 3d58695e
      Paul Mundt authored
      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: default avatarPaul Mundt <lethal@linux-sh.org>
    • Paul Mundt's avatar
      sh: Kill off duplicate page fault notifiers in slow path. · 8f2baee2
      Paul Mundt authored
      We already have hooks in place in the __do_page_fault() fast-path,
      so kill them off in the slow path.
      Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
    • Paul Mundt's avatar
  27. 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>