1. 25 May, 2004 3 commits
    • Andrew Morton's avatar
      [PATCH] ppc64: NUMA fixes · 55d130a5
      Andrew Morton authored
      From: Anton Blanchard <anton@samba.org>
      
      From: Anton Blanchard, Dave Hansen and Olof Johansson:
      
      Fix multiple bugs in the ppc64 NUMA topology probe code.
      
      - We were using HW cpu numbers instead of logical ones.  615, 630, 650,
        some 670 and some 690 SMP will all fail to boot without this patch.
      
      - The old code would BUG() when it got confused (more NUMA zones than the
        kernel is configured for etc).
      
      - The common depth calculation was incorrect.  Dave found an OF property
        that gives us exactly what we want.
      
      - Things were broken on SMT machines.
      
      The new code should work on those broken systems and should no longer BUG()
      but fall back to a flat topology when it gets confused.
      55d130a5
    • Andrew Morton's avatar
      [PATCH] ppc64: fix inline spinlocks · 2c725188
      Andrew Morton authored
      From: Anton Blanchard <anton@samba.org>
      
      In _raw_spin_lock_flags we were branching to the wrong spot and would
      restore random stuff to the MSR.
      2c725188
    • Dave Jones's avatar
      [PATCH] Make early_cpu_detect() set x86_cache_alignment on pre-cpuid CPU's too · 4b796a9f
      Dave Jones authored
      From: Zdenek Pavlas <pavlas@nextra.cz>
      
      On any x86 without cpuid, early_cpu_detect() left x86_cache_alignment as
      zero, so kmem_cache_init() calls cache_estimate() with align == 0, and
      it loops forever. I've tried this trivial fix, and it works for me.
      
      Andi Kleen looked over this, and ok'd it.
      4b796a9f
  2. 24 May, 2004 2 commits
    • Paul Mackerras's avatar
      [PATCH] ppc64: better stack traces · 14bc28ad
      Paul Mackerras authored
      This improves the stack traces we get on PPC64 by putting a marker in
      those stack frames that are created as a result of an interrupt or
      exception.  The marker is "regshere" (0x7265677368657265).
      
      With this, stack traces show where exceptions have occurred, which can
      be very useful.  This also improves the accuracy of the trace because
      the relevant return address can be in the link register at the time of
      the exception rather than on the stack.  We now print the PC and
      exception type for each exception frame, and then the link register if
      appropriate as the next item in the trace.
      14bc28ad
    • Linus Torvalds's avatar
      Merge bk://bk.arm.linux.org.uk/linux-2.6-rmk · e1ff5fe0
      Linus Torvalds authored
      into ppc970.osdl.org:/home/torvalds/v2.6/linux
      e1ff5fe0
  3. 25 May, 2004 1 commit
  4. 24 May, 2004 15 commits
  5. 23 May, 2004 18 commits
  6. 22 May, 2004 1 commit