1. 17 10月, 2007 1 次提交
    • A
      [POWERPC] Enable SLUB in *_defconfig · 309a1092
      Anton Blanchard 提交于
      When checking out the new NO_HZ support in powerpc, I noticed we never
      slept for more than 2 seconds.  It turns out SLAB has a 2 second per cpu
      timer that causes this.
      
      After switching to SLUB I see some nice 4 second sleeps which is the
      limit on this POWER6 box (the decrementer ticks at 512MHz):
      
      slept 4.19 sec
      slept 4.19 sec
      slept 4.19 sec
      slept 4.19 sec
      slept 3.96 sec
      slept 3.80 sec
      slept 2.99 sec
      
      Since SLUB is now the default and some powerpc defconfigs already enable
      it, lets enable SLUB across the board for consistency.  While doing this
      I also noticed that the maple defconfig has SLAB debugging enabled which
      is sure to make your box nice and slow.  Fix that too.
      Signed-off-by: NAnton Blanchard <anton@samba.org>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      309a1092
  2. 30 8月, 2007 1 次提交
  3. 26 6月, 2007 1 次提交
  4. 10 5月, 2007 1 次提交
  5. 07 2月, 2007 1 次提交
  6. 22 1月, 2007 1 次提交
  7. 19 12月, 2006 1 次提交
  8. 04 12月, 2006 2 次提交
    • A
      [POWERPC] update cell_defconfig for ps3 support · 1c72db14
      Arnd Bergmann 提交于
      In the common cell kernel, I want to have ps3 enabled
      to find potential bugs at compile-time.
      Also enable SPU disassembly in xmon.
      Signed-off-by: NArnd Bergmann <arnd.bergmann@de.ibm.com>
      1c72db14
    • M
      [POWERPC] cell: Add oprofile support · 18f2190d
      Maynard Johnson 提交于
      Add PPU event-based and cycle-based profiling support to Oprofile for Cell.
      
      Oprofile is expected to collect data on all CPUs simultaneously.
      However, there is one set of performance counters per node.  There are
      two hardware threads or virtual CPUs on each node.  Hence, OProfile must
      multiplex in time the performance counter collection on the two virtual
      CPUs.
      
      The multiplexing of the performance counters is done by a virtual
      counter routine.  Initially, the counters are configured to collect data
      on the even CPUs in the system, one CPU per node.  In order to capture
      the PC for the virtual CPU when the performance counter interrupt occurs
      (the specified number of events between samples has occurred), the even
      processors are configured to handle the performance counter interrupts
      for their node.  The virtual counter routine is called via a kernel
      timer after the virtual sample time.  The routine stops the counters,
      saves the current counts, loads the last counts for the other virtual
      CPU on the node, sets interrupts to be handled by the other virtual CPU
      and restarts the counters, the virtual timer routine is scheduled to run
      again.  The virtual sample time is kept relatively small to make sure
      sampling occurs on both CPUs on the node with a relatively small
      granularity.  Whenever the counters overflow, the performance counter
      interrupt is called to collect the PC for the CPU where data is being
      collected.
      
      The oprofile driver relies on a firmware RTAS call to setup the debug bus
      to route the desired signals to the performance counter hardware to be
      counted.  The RTAS call must set the routing registers appropriately in
      each of the islands to pass the signals down the debug bus as well as
      routing the signals from a particular island onto the bus.  There is a
      second firmware RTAS call to reset the debug bus to the non pass thru
      state when the counters are not in use.
      Signed-off-by: NCarl Love <carll@us.ibm.com>
      Signed-off-by: NMaynard Johnson <mpjohn@us.ibm.com>
      Signed-off-by: NArnd Bergmann <arnd.bergmann@de.ibm.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      18f2190d
  9. 25 10月, 2006 3 次提交
  10. 05 10月, 2006 1 次提交
  11. 10 9月, 2006 1 次提交
  12. 28 6月, 2006 1 次提交
  13. 21 6月, 2006 3 次提交
  14. 29 4月, 2006 1 次提交
  15. 27 3月, 2006 1 次提交
  16. 16 3月, 2006 1 次提交
  17. 19 1月, 2006 1 次提交
  18. 20 12月, 2005 1 次提交
  19. 16 11月, 2005 1 次提交
  20. 03 11月, 2005 1 次提交
  21. 20 10月, 2005 1 次提交
  22. 09 8月, 2005 1 次提交
  23. 28 7月, 2005 1 次提交
  24. 15 6月, 2005 1 次提交
  25. 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