1. 08 Jun, 2009 1 commit
  2. 18 May, 2009 1 commit
    • Mel Gorman's avatar
      [ARM] Double check memmap is actually valid with a memmap has unexpected holes V2 · eb33575c
      Mel Gorman authored
      
      
      pfn_valid() is meant to be able to tell if a given PFN has valid memmap
      associated with it or not. In FLATMEM, it is expected that holes always
      have valid memmap as long as there is valid PFNs either side of the hole.
      In SPARSEMEM, it is assumed that a valid section has a memmap for the
      entire section.
      
      However, ARM and maybe other embedded architectures in the future free
      memmap backing holes to save memory on the assumption the memmap is never
      used. The page_zone linkages are then broken even though pfn_valid()
      returns true. A walker of the full memmap must then do this additional
      check to ensure the memmap they are looking at is sane by making sure the
      zone and PFN linkages are still valid. This is expensive, but walkers of
      the full memmap are extremely rare.
      
      This was caught before for FLATMEM and hacked around but it hits again for
      SPARSEMEM because the page_zone linkages can look ok where the PFN linkages
      are totally screwed. This looks like a hatchet job but the reality is that
      any clean solution would end up consumning all the memory saved by punching
      these unexpected holes in the memmap. For example, we tried marking the
      memmap within the section invalid but the section size exceeds the size of
      the hole in most cases so pfn_valid() starts returning false where valid
      memmap exists. Shrinking the size of the section would increase memory
      consumption offsetting the gains.
      
      This patch identifies when an architecture is punching unexpected holes
      in the memmap that the memory model cannot automatically detect and sets
      ARCH_HAS_HOLES_MEMORYMODEL. At the moment, this is restricted to EP93xx
      which is the model sub-architecture this has been reported on but may expand
      later. When set, walkers of the full memmap must call memmap_valid_within()
      for each PFN and passing in what it expects the page and zone to be for
      that PFN. If it finds the linkages to be broken, it assumes the memmap is
      invalid for that PFN.
      Signed-off-by: default avatarMel Gorman <mel@csn.ul.ie>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      eb33575c
  3. 05 May, 2009 1 commit
  4. 30 Apr, 2009 4 commits
  5. 26 Apr, 2009 2 commits
  6. 23 Apr, 2009 2 commits
  7. 26 Mar, 2009 2 commits
  8. 22 Mar, 2009 5 commits
  9. 15 Mar, 2009 1 commit
    • Nicolas Pitre's avatar
      [ARM] add CONFIG_HIGHMEM option · 053a96ca
      Nicolas Pitre authored
      
      
      Here it is... HIGHMEM for the ARM architecture.  :-)
      
      If you don't have enough ram for highmem pages to be allocated and still
      want to test this, then the cmdline option "vmalloc=" can be used with
      a value large enough to force the highmem threshold down.
      
      Successfully tested on a Marvell DB-78x00-BP Development Board with
      2 GB of RAM.
      Signed-off-by: default avatarNicolas Pitre <nico@marvell.com>
      053a96ca
  10. 21 Feb, 2009 1 commit
  11. 12 Feb, 2009 1 commit
  12. 06 Jan, 2009 1 commit
  13. 20 Dec, 2008 2 commits
  14. 15 Dec, 2008 1 commit
  15. 14 Dec, 2008 1 commit
  16. 12 Dec, 2008 1 commit
  17. 09 Dec, 2008 2 commits
  18. 03 Dec, 2008 1 commit
  19. 01 Dec, 2008 1 commit
  20. 30 Nov, 2008 1 commit
  21. 27 Nov, 2008 6 commits
  22. 23 Oct, 2008 1 commit
    • Steven Rostedt's avatar
      ftrace: disable dynamic ftrace for all archs that use daemon · 07c4cc1c
      Steven Rostedt authored
      
      
      The ftrace daemon is complex and can cause nasty races if something goes
      wrong. Since it affects all of the kernel, this patch disables dynamic
      ftrace from any arch that depends on the daemon. Until the archs are
      ported over to the new MCOUNT_RECORD method, I am disabling dynamic
      ftrace from them.
      
      Note: I am leaving in the arch/<arch>/kernel/ftrace.c code alone since
      that can be used when the arch is ported to MCOUNT_RECORD. To port
      the arch to MCOUNT_RECORD, the scripts/recordmcount.pl needs to be
      updated. I will make that easier to do for 2.6.29. For 28, we will keep
      the archs disabled.
      Signed-off-by: default avatarSteven Rostedt <srostedt@redhat.com>
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      07c4cc1c
  23. 22 Oct, 2008 1 commit
    • Brian Swetland's avatar
      [ARM] msm: rename ARCH_MSM7X00A to ARCH_MSM · 1637de0c
      Brian Swetland authored
      
      
      The MSM architecture covers a wider family of chips than just the MSM7X00A.
      Move to a more generic name, in perparation for supporting the specific
      SoC variants as sub-architectures (ARCH_MSM7X01A, ARCH_MSM722X, etc).  This
      gives us ARCH_MSM for the (many) common peripherals.
      
      This also removes the unused/obsolete config item MSM7X00A_IDLE.
      Signed-off-by: default avatarBrian Swetland <swetland@google.com>
      1637de0c