1. 06 9月, 2005 20 次提交
  2. 05 9月, 2005 4 次提交
    • N
      [PATCH] ppc64: replace schedule_timeout() with msleep_interruptible() · 0287ebed
      Nishanth Aravamudan 提交于
      Use msleep_interruptible() instead of schedule_timeout() in ppc64-specific
      code to cleanup/simplify the sleeping logic.  Change the units of the
      parameter of do_event_scan_all_cpus() to milliseconds from jiffies.  The
      return value of rtas_extended_busy_delay_time() was incorrectly being used
      as a jiffies value (it is actually milliseconds), which is fixed by using
      the value as a parameter to msleep_interruptible().  Also, use
      rtas_extended_busy_delay_time() in another case where similar logic is
      duplicated.
      Signed-off-by: NNishanth Aravamudan <nacc@us.ibm.com>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      0287ebed
    • O
      [PATCH] ppc64: Add VMX save flag to VPA · 233ccd0d
      Olof Johansson 提交于
      We need to indicate to the hypervisor that it needs to save our VMX
      registers when switching partitions on a shared-processor system, just as
      it needs to for FP and PMC registers.
      
      This could be made to be on-demand when VMX is used, but we don't do that
      for FP nor PMC right now either so let's not overcomplicate things.
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      Acked-by: NPaul Mackerras <paulus@samba.org>
      Cc: Anton Blanchard <anton@samba.org>
      Cc: <engebret@us.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      233ccd0d
    • O
      [PATCH] ppc64: update xmon helptext · b749bfcd
      Olaf Hering 提交于
      xmon will do nothing but noise on a G5 if BOOTX_TEXT is not enabled.
      mention the recognized kernel cmdline options for xmon.
      Signed-off-by: NOlaf Hering <olh@suse.de>
      Cc: Paul Mackeras <paulus@samba.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      b749bfcd
    • B
      [PATCH] SPARSEMEM EXTREME · 802f192e
      Bob Picco 提交于
      A new option for SPARSEMEM is ARCH_SPARSEMEM_EXTREME.  Architecture
      platforms with a very sparse physical address space would likely want to
      select this option.  For those architecture platforms that don't select the
      option, the code generated is equivalent to SPARSEMEM currently in -mm.
      I'll be posting a patch on ia64 ml which uses this new SPARSEMEM feature.
      
      ARCH_SPARSEMEM_EXTREME makes mem_section a one dimensional array of
      pointers to mem_sections.  This two level layout scheme is able to achieve
      smaller memory requirements for SPARSEMEM with the tradeoff of an
      additional shift and load when fetching the memory section.  The current
      SPARSEMEM -mm implementation is a one dimensional array of mem_sections
      which is the default SPARSEMEM configuration.  The patch attempts isolates
      the implementation details of the physical layout of the sparsemem section
      array.
      
      ARCH_SPARSEMEM_EXTREME depends on 64BIT and is by default boolean false.
      
      I've boot tested under aim load ia64 configured for ARCH_SPARSEMEM_EXTREME.
       I've also boot tested a 4 way Opteron machine with !ARCH_SPARSEMEM_EXTREME
      and tested with aim.
      Signed-off-by: NAndy Whitcroft <apw@shadowen.org>
      Signed-off-by: NBob Picco <bob.picco@hp.com>
      Signed-off-by: NDave Hansen <haveblue@us.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      802f192e
  3. 02 9月, 2005 1 次提交
  4. 30 8月, 2005 14 次提交
  5. 29 8月, 2005 1 次提交
    • D
      [PATCH] Dynamic hugepage addresses for ppc64 · c594adad
      David Gibson 提交于
      Paulus, I think this is now a reasonable candidate for the post-2.6.13
      queue.
      
      Relax address restrictions for hugepages on ppc64
      
      Presently, 64-bit applications on ppc64 may only use hugepages in the
      address region from 1-1.5T.  Furthermore, if hugepages are enabled in
      the kernel config, they may only use hugepages and never normal pages
      in this area.  This patch relaxes this restriction, allowing any
      address to be used with hugepages, but with a 1TB granularity.  That
      is if you map a hugepage anywhere in the region 1TB-2TB, that entire
      area will be reserved exclusively for hugepages for the remainder of
      the process's lifetime.  This works analagously to hugepages in 32-bit
      applications, where hugepages can be mapped anywhere, but with 256MB
      (mmu segment) granularity.
      
      This patch applies on top of the four level pagetable patch
      (http://patchwork.ozlabs.org/linuxppc64/patch?id=1936).
      Signed-off-by: NDavid Gibson <dwg@au1.ibm.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      c594adad