Re: [Patch 1/1] PPC64-HWBKPT: Implement hw-breakpoints for PPC64

2010-03-14 Thread K.Prasad
On Fri, Mar 12, 2010 at 05:19:36PM +1100, Benjamin Herrenschmidt wrote: > > > Index: linux-2.6.ppc64_test/arch/powerpc/include/asm/hw_breakpoint.h > > === > > --- /dev/null > > +++ linux-2.6.ppc64_test/arch/powerpc/include/asm/hw_brea

Re: Problem with PCI bus rescan on 460EX

2010-03-14 Thread Felix Radensky
Hello Kenji-san, Kenji Kaneshige wrote: Felix Radensky wrote: Hello Kenji-san, Kenji Kaneshige wrote: I'm not sure, but I guess pci_setup_bridge() didn't update IO base/limit and Mem base/limit of the bridge (:00:02.0) because of the following lines. static void pci_setup_bridge(struct

Re: Problem with PCI bus rescan on 460EX

2010-03-14 Thread Benjamin Herrenschmidt
On Mon, 2010-03-15 at 16:46 +1100, Benjamin Herrenschmidt wrote: > On Mon, 2010-03-15 at 14:39 +0900, Kenji Kaneshige wrote: > > > > > Yes, with these lines removed bridge memory window is properly > > allocated. > > > > These lines are to prevent updating IO or memory windows when there > > are

Re: Problem with PCI bus rescan on 460EX

2010-03-14 Thread Benjamin Herrenschmidt
On Mon, 2010-03-15 at 14:39 +0900, Kenji Kaneshige wrote: > > > Yes, with these lines removed bridge memory window is properly > allocated. > > These lines are to prevent updating IO or memory windows when there > are > some devices working behind the bridge. So please note that removing > these

[PATCH] powerpc/perf_events: Implement perf_arch_fetch_caller_regs for powerpc

2010-03-14 Thread Paul Mackerras
This implements a powerpc version of perf_arch_fetch_caller_regs. It's implemented in assembly because that way we can be sure there isn't a stack frame for perf_arch_fetch_caller_regs. If it was in C, gcc might or might not create a stack frame for it, which would affect the number of levels we h

Re: Problem with PCI bus rescan on 460EX

2010-03-14 Thread Kenji Kaneshige
Felix Radensky wrote: Hello Kenji-san, Kenji Kaneshige wrote: I'm not sure, but I guess pci_setup_bridge() didn't update IO base/limit and Mem base/limit of the bridge (:00:02.0) because of the following lines. static void pci_setup_bridge(struct pci_bus *bus) { struct pci_dev *brid

Re: 2.6.34-rc1: Badness at fs/proc/generic.c:316

2010-03-14 Thread Benjamin Herrenschmidt
On Sun, 2010-03-14 at 12:51 +0100, Andreas Schwab wrote: > Christian Kujau writes: > > > On Sun, 14 Mar 2010 at 13:24, Alexey Dobriyan wrote: > >> Post "find /proc/device-tree" output. > > > > I did upload[0] a tarball of /proc/device-tree, please see below the > > "find" output. > > > > Indeed,

Re: [BUGFIX][PATCH] memcg: avoid use cmpxchg in swap cgroup maintainance (Was Re: 34-rc1-git3 build failure with CGROUP_MEM_RES_CTLR_SWAP=y

2010-03-14 Thread Daisuke Nishimura
On Mon, 15 Mar 2010 10:02:02 +0900 KAMEZAWA Hiroyuki wrote: > On Sun, 14 Mar 2010 16:18:06 +0530 > Sachin Sant wrote: > > > On a PowerPC box, latest 34-rc1 git(d89b218b8...) fails to build > > with CGROUPS_MEM_RES_CTRL_SWAP=y. > > > > LD init/built-in.o > > LD .tmp_vmlinux1 > > mm/b

Re: [BUGFIX][PATCH] memcg: avoid use cmpxchg in swap cgroup maintainance (Was Re: 34-rc1-git3 build failure with CGROUP_MEM_RES_CTLR_SWAP=y

2010-03-14 Thread Benjamin Herrenschmidt
> Oh..ok, powerpc (and other archs?) can't do 2byte cmpxchg and xchg. > Then, we should use spinlock rather than that. > > How about this ? Nishimura-san, could you consider something better ? > We need a quick fix. sparc64 is the same as powerpc in that regard, maybe others. Cheers, Ben. > =

Re: [BUGFIX][PATCH] memcg: avoid use cmpxchg in swap cgroup maintainance (Was Re: 34-rc1-git3 build failure with CGROUP_MEM_RES_CTLR_SWAP=y

2010-03-14 Thread Balbir Singh
* KAMEZAWA Hiroyuki [2010-03-15 10:02:02]: > On Sun, 14 Mar 2010 16:18:06 +0530 > Sachin Sant wrote: > > > On a PowerPC box, latest 34-rc1 git(d89b218b8...) fails to build > > with CGROUPS_MEM_RES_CTRL_SWAP=y. > > > > LD init/built-in.o > > LD .tmp_vmlinux1 > > mm/built-in.o: In fun

[BUGFIX][PATCH] memcg: avoid use cmpxchg in swap cgroup maintainance (Was Re: 34-rc1-git3 build failure with CGROUP_MEM_RES_CTLR_SWAP=y

2010-03-14 Thread KAMEZAWA Hiroyuki
On Sun, 14 Mar 2010 16:18:06 +0530 Sachin Sant wrote: > On a PowerPC box, latest 34-rc1 git(d89b218b8...) fails to build > with CGROUPS_MEM_RES_CTRL_SWAP=y. > > LD init/built-in.o > LD .tmp_vmlinux1 > mm/built-in.o: In function __xchg: > arch/powerpc/include/asm/system.h:331: undefine

Re: 34-rc1-git3 build failure with CGROUP_MEM_RES_CTLR_SWAP=y

2010-03-14 Thread Michael Ellerman
On Sun, 2010-03-14 at 16:18 +0530, Sachin Sant wrote: > On a PowerPC box, latest 34-rc1 git(d89b218b8...) fails to build > with CGROUPS_MEM_RES_CTRL_SWAP=y. > > LD init/built-in.o > LD .tmp_vmlinux1 > mm/built-in.o: In function __xchg: > arch/powerpc/include/asm/system.h:331: undefined

Re: 2.6.34-rc1: Badness at fs/proc/generic.c:316

2010-03-14 Thread Andreas Schwab
Christian Kujau writes: > On Sun, 14 Mar 2010 at 13:24, Alexey Dobriyan wrote: >> Post "find /proc/device-tree" output. > > I did upload[0] a tarball of /proc/device-tree, please see below the > "find" output. > > Indeed, there's a /cpus/PowerPC,g...@0/l2-cache and > /cpus/PowerPC,g...@0/l2-cac

Re: 2.6.34-rc1: Badness at fs/proc/generic.c:316

2010-03-14 Thread Alexey Dobriyan
On Sun, Mar 14, 2010 at 03:39:39AM -0700, Christian Kujau wrote: > On Sun, 14 Mar 2010 at 08:55, Alexey Dobriyan wrote: > > > device-tree: Duplicate name in /cpus/PowerPC,g...@0, renamed to > > > "l2-cache#1" > > > name 'pulses/rev' > > > > Uh-oh. > > Uh-oh? :-) > > >> Is this something to worr

34-rc1-git3 build failure with CGROUP_MEM_RES_CTLR_SWAP=y

2010-03-14 Thread Sachin Sant
On a PowerPC box, latest 34-rc1 git(d89b218b8...) fails to build with CGROUPS_MEM_RES_CTRL_SWAP=y. LD init/built-in.o LD .tmp_vmlinux1 mm/built-in.o: In function __xchg: arch/powerpc/include/asm/system.h:331: undefined reference to .__xchg_called_with_bad_pointer mm/built-in.o: In fu

Re: 2.6.34-rc1: Badness at fs/proc/generic.c:316

2010-03-14 Thread Christian Kujau
On Sun, 14 Mar 2010 at 08:55, Alexey Dobriyan wrote: > > device-tree: Duplicate name in /cpus/PowerPC,g...@0, renamed to "l2-cache#1" > > name 'pulses/rev' > > Uh-oh. Uh-oh? :-) >> Is this something to worry about? The machine seems to run fine so far... > > Runtime behaviour remains the same,