1. 08 7月, 2009 1 次提交
  2. 16 6月, 2009 1 次提交
  3. 04 8月, 2008 1 次提交
  4. 21 6月, 2006 1 次提交
    • A
      [POWERPC] Fix mdelay badness on shared processor partitions · 1e92a550
      Anton Blanchard 提交于
      On partitioned PPC64 systems where a partition is given 1/10 of a
      processor, we have seen mdelay() delaying for 10 times longer than it
      should.  The reason is that the generic mdelay(n) does n delays of 1
      millisecond each.  However, with 1/10 of a processor, we only get a
      one-millisecond timeslice every 10ms.  Thus each 1 millisecond delay
      loop ends up taking 10ms elapsed time.
      
      The solution is just to use the PPC64 udelay function, which uses the
      timebase to ensure that the delay is based on elapsed time rather than
      how much processing time the partition has been given.  (Yes, the
      generic mdelay uses the PPC64 udelay, but the problem is that the
      start time gets reset every millisecond, and each time it gets reset
      we lose another 9ms.)
      Signed-off-by: NAnton Blanchard <anton@samba.org>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      Acked-by: NAndrew Morton <akpm@osdl.org>
      1e92a550
  5. 09 1月, 2006 1 次提交
  6. 18 11月, 2005 1 次提交
    • P
      powerpc: Fix delay functions for 601 processors · 6defa38b
      Paul Mackerras 提交于
      My earlier merge of delay.h introduced a timebase-based udelay for
      32-bit machines but also broke the 601, which doesn't have the
      timebase register.  This fixes it by using the 601's RTC register on
      the 601, and also moves __delay() and udelay() to be out-of-line in
      arch/powerpc/kernel/time.c.  These functions aren't really performance
      critical, after all.
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      6defa38b
  7. 14 11月, 2005 1 次提交
  8. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4