Re: [RFC][PATCH] irq: support IRQ_NESTED_THREAD with non-threaded interrupt handlers

2010-06-07 Thread Thomas Gleixner
On Mon, 7 Jun 2010, Esben Haabendal wrote: > On Mon, Jun 7, 2010 at 5:06 PM, Thomas Gleixner wrote: > > > Maybe you understand now, why I was pretty sure upfront, that your > > approach was wrong even without knowing all the gory details ? :) > > I understand. There is a better solution, which

Re: [PATCH] agp/uninorth: Fix oops caused by flushing too much

2010-06-07 Thread Michel Dänzer
On Mit, 2010-06-02 at 15:33 +1000, Paul Mackerras wrote: > This fixes a sporadic oops at boot on G5 Power Macs. The table_end > variable has the address of the last byte of the table. Adding on > PAGE_SIZE means we flush too much, and if the page after the table > is not mapped for any reason, t

[PATCH 3/3] powerpc: enabled asymmetric SMT scheduling on POWER7

2010-06-07 Thread Michael Neuling
The POWER7 core has dynamic SMT mode switching which is controlled by the hypervisor. There are 3 SMT modes: SMT1 uses thread 0 SMT2 uses threads 0 & 1 SMT4 uses threads 0, 1, 2 & 3 When in any particular SMT mode, all threads have the same performance as each other (ie. a

[PATCH 2/3] sched: add asymmetric group packing option for sibling domain

2010-06-07 Thread Michael Neuling
Check to see if the group is packed in a sched doman. This is primarily intended to used at the sibling level. Some cores like POWER7 prefer to use lower numbered SMT threads. In the case of POWER7, it can move to lower SMT modes only when higher threads are idle. When in lower SMT modes, the t

[PATCH 1/3] sched: fix capacity calculations for SMT4

2010-06-07 Thread Michael Neuling
From: Srivatsa Vaddagiri Handle cpu capacity being reported as 0 on cores with more number of hardware threads. For example on a Power7 core with 4 hardware threads, core power is 1177 and thus power of each hardware thread is 1177/4 = 294. This low power can lead to capacity for each hardware th

[PATCH 0/3] sched: asymmetrical packing for POWER7 SMT4

2010-06-07 Thread Michael Neuling
This patch series implements asymmetric SMT packing which ensures consistently good performance on POWER7. Without this series, tasks will vary in performance by around +/-30% on POWER7 This new version is based on help from Vatsa and Vaidy in an attempt to answer concerns that Peter Zijlstra had

[PATCH] powerpc: Move kdump default base address to 64MB on 64bit

2010-06-07 Thread Anton Blanchard
We are seeing boot fails on some System p machines when using the kdump crashkernel= boot option. The default kdump base address is 32MB, so if we reserve 256MB for kdump then we reserve all of the RMO except the first 32MB. We really want kdump to reserve some memory in the RMO and most of it el

[PATCH] powerpc/boot: Remove addRamdisk.c since it is now unused

2010-06-07 Thread Paul Mackerras
It was used in the dim distant past for adding initrds to images for legacy iSeries, but it's not even used for that now that we have initramfs. So remove it. Signed-off-by: Paul Mackerras --- arch/powerpc/boot/Makefile |2 +- arch/powerpc/boot/addRamDisk.c | 311 --

Re: [RFC][PATCH] irq: support IRQ_NESTED_THREAD with non-threaded interrupt handlers

2010-06-07 Thread Thomas Gleixner
On Mon, 7 Jun 2010, Esben Haabendal wrote: > On Mon, Jun 7, 2010 at 5:06 PM, Thomas Gleixner wrote: > > > Maybe you understand now, why I was pretty sure upfront, that your > > approach was wrong even without knowing all the gory details ? :) > > I understand. There is a better solution, which

Re: [RFC][PATCH] irq: support IRQ_NESTED_THREAD with non-threaded interrupt handlers

2010-06-07 Thread Esben Haabendal
On Mon, Jun 7, 2010 at 5:06 PM, Thomas Gleixner wrote: > Maybe you understand now, why I was pretty sure upfront, that your > approach was wrong even without knowing all the gory details ? :) I understand. There is a better solution, which is to use threaded interrupts where needed. But I must

[PATCH] powerpc: Fix integer constant warning

2010-06-07 Thread Steve Best
Fix ppc arch/powerpc/boot/addRamDisk.c:277: warning: integer constant is too large for 'long' type Signed-off-by: Steve Best diff -purN linux.2.6.orig/arch/powerpc/boot/addRamDisk.c linux.2.6/arch/powerpc/boot/addRamDisk.c --- linux.2.6.orig/arch/powerpc/boot/addRamDisk.c 2010-06-07 15:2

Re: [RFC][PATCH] irq: support IRQ_NESTED_THREAD with non-threaded interrupt handlers

2010-06-07 Thread Thomas Gleixner
On Mon, 7 Jun 2010, Esben Haabendal wrote: > On Mon, 2010-06-07 at 00:08 +0200, Thomas Gleixner wrote: > > > > The only reason for the buslock in the pca9535 driver is to set the > > > direction (ie. input) for interrupt pins. On powerpc, I do this in the > > > map() > > > irq_chip function. So

Re: [PATCH 1/5] sched: fix capacity calculations for SMT4

2010-06-07 Thread Srivatsa Vaddagiri
On Mon, May 31, 2010 at 10:33:16AM +0200, Peter Zijlstra wrote: > On Fri, 2010-04-16 at 15:58 +0200, Peter Zijlstra wrote: > > > > > > Hrmm, my brain seems muddled but I might have another solution, let me > > ponder this for a bit.. > > > > Right, so the thing I was thinking about is taking th

Re: [RFC][PATCH] irq: support IRQ_NESTED_THREAD with non-threaded interrupt handlers

2010-06-07 Thread Esben Haabendal
On Mon, 2010-06-07 at 00:08 +0200, Thomas Gleixner wrote: > > The only reason for the buslock in the pca9535 driver is to set the > > direction (ie. input) for interrupt pins. On powerpc, I do this in the > > map() > > irq_chip function. So I don't see the need for buslock on powerpc. > > What'

Re: [PATCH] powerpc: Disable CONFIG_SYSFS_DEPRECATED

2010-06-07 Thread Anton Blanchard
Hi Josh, > Yes actually. I've tested on a few boards and it seems to be working well > enough. My apologies for not replying sooner. > > Acked-by: Josh Boyer Thanks for testing! Anton ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org htt

Re: [PATCH] powerpc: Disable CONFIG_SYSFS_DEPRECATED

2010-06-07 Thread Josh Boyer
On Mon, Jun 07, 2010 at 10:46:57AM +1000, Anton Blanchard wrote: > >Hi Josh, > >> I'd like to run a few tests with this disabled on the 4xx boards first >> please. >> I can't say that all the boards I have will have any sort of "distro" to >> begin >> with, and if they did they might not be runni

Re: [PATCH 1/2] powerpc: ipic: use set_irq_chip to ensure irq_chip defaults are applied

2010-06-07 Thread Benjamin Herrenschmidt
On Mon, 2010-06-07 at 12:22 +0200, Thomas Gleixner wrote: > > Would it be better to change the call order in __setup_irq(), and > > call irq_chip_set_defaults after __irq_set_trigger() ? Or perhaps > > even calling it twice (again after __irq_set_trigger()) ? > > Grmpf, set_type() was never mea

Re: [Patch 0/5] PPC64-HWBKPT: Hardware Breakpoint interfaces - ver XXII

2010-06-07 Thread Paul Mackerras
On Mon, Jun 07, 2010 at 12:33:51PM +0530, K.Prasad wrote: > Given that 'ptrace_bps' is used only for ptrace originated breakpoints > and that we return early i.e. before detecting extraneous interrupts > in hw_breakpoint_handler() (as shown above) they shouldn't overlap each > other. The following

Re: [PATCH 2/2] gpio: pca953x: add powerpc irq support

2010-06-07 Thread Thomas Gleixner
On Mon, 7 Jun 2010, Esben Haabendal wrote: > On Mon, 2010-06-07 at 01:39 +0200, Thomas Gleixner wrote: > > On Fri, 4 Jun 2010, Esben Haabendal wrote: > > > > @@ -120,6 +124,10 @@ static int pca953x_gpio_direction_input(struct > > > gpio_chip *gc, unsigned off) > > > chip = container_of(gc, stru

Re: [PATCH 1/2] powerpc: ipic: use set_irq_chip to ensure irq_chip defaults are applied

2010-06-07 Thread Thomas Gleixner
On Mon, 7 Jun 2010, Esben Haabendal wrote: > On Mon, 2010-06-07 at 01:45 +0200, Thomas Gleixner wrote: > > > This patch has never been tested with spinlock debugging enabled and > > will break SMP as it causes a deadlock on irq_desc->lock. > > > > Again: See Documentation/Submit* > > Ok, will d

Re: [Patch 0/5] PPC64-HWBKPT: Hardware Breakpoint interfaces - ver XXII

2010-06-07 Thread K.Prasad
On Fri, Jun 04, 2010 at 07:06:48PM +1000, Paul Mackerras wrote: > On Fri, Jun 04, 2010 at 12:21:45PM +0530, K.Prasad wrote: > > > Meanwhile I tested the per-cpu breakpoints with the new emulate_step > > patch (refer linuxppc-dev message-id: > > 20100602112903.gb30...@brick.ozlabs.ibm.com) and they