Re: [PATCH][RFC] preempt_count corruption across H_CEDE call with CONFIG_PREEMPT on pseries

2010-08-06 Thread Darren Hart
On 08/05/2010 10:09 PM, Vaidyanathan Srinivasan wrote: > * Darren Hart [2010-08-05 19:19:00]: > >> On 07/22/2010 10:09 PM, Benjamin Herrenschmidt wrote: >>> On Thu, 2010-07-22 at 21:44 -0700, Darren Hart wrote: >>> suggestion I updated the instrumentation to display the local_save_fl

Re: [PATCH] powerpc: inline ppc64_runlatch_off

2010-08-06 Thread Olof Johansson
On Fri, Aug 06, 2010 at 02:53:15PM +1000, Anton Blanchard wrote: > > I'm sick of seeing ppc64_runlatch_off in our profiles, so inline the > heavily used part of it into the callers. To avoid a mess of circular includes > I didn't add it as an inline function. > > Signed-off-by: Anton Blanchard >

How to disable eTSEC2 in MPC837xerdb

2010-08-06 Thread Ravi Gupta
Hi, I am trying to disable eTSEC2 in mpc8377erdb freescale board. I had removed the entry corresponding to enet2 from the dts file and updated the firmware to use the new dtb file. Now when I boot the board I can still see the eth1 entry in the ifconfig -a output. Is there something that I am miss

Re: [PATCH] powerpc: inline ppc64_runlatch_off

2010-08-06 Thread Anton Blanchard
Hi Olof, > No semicolon here. Nice catch! Anton I'm sick of seeing ppc64_runlatch_off in our profiles, so inline it into the callers. To avoid a mess of circular includes I didn't add it as an inline function. Signed-off-by: Anton Blanchard --- Index: powerpc.git/arch/powerpc/include/asm/r

Re: [PATCH 00/27] KVM PPC PV framework v3

2010-08-06 Thread Kumar Gala
On Jul 29, 2010, at 7:47 AM, Alexander Graf wrote: > [without] > > debian-powerpc:~# time for i in {1..1000}; do /bin/echo hello > /dev/null; > done > > real0m14.659s > user0m8.967s > sys 0m5.688s > > [with] > > debian-powerpc:~# time for i in {1..1000}; do /bin/echo hello > /dev

[PATCH] powerpc: fix i8042 module build error

2010-08-06 Thread Grant Likely
of_i8042_{kbd,aux}_irq needs to be exported Signed-off-by: Grant Likely --- Stephen and Ben, this fixes up the build error in linux-next. If you prefer, I can stuff this patch into my next-powerpc branch. Ben, I've got other commits in that branch that I'll be sending to you early next week an

Re: [PATCH 0/2 v3] mpc5200 ac97 gpio reset

2010-08-06 Thread Grant Likely
On Thu, Aug 5, 2010 at 6:59 AM, Eric Millbrandt wrote: >> -Original Message- >> From: linuxppc-dev-bounces+emillbrandt=dekaresearch@lists.ozlabs.org >> [mailto:linuxppc-dev- >> bounces+emillbrandt=dekaresearch@lists.ozlabs.org] On Behalf Of Mark >> Brown >> Sent: Tuesday, August 03

Re: Relocating bootwrapper causes kernel panic

2010-08-06 Thread Benjamin Herrenschmidt
\ > Probably. You won't have any page tables yet, much less an entry for > the device tree. > > > >> I think the cause is clear now. But how to fix it? Two questions: > > >> 2. If the DTLB miss exception handler is not the right guy to load a > > >> proper TLB entry, how can I set one entry based

Re: [PATCH] powerpc: fix i8042 module build error

2010-08-06 Thread Stephen Rothwell
Hi Grant, On Fri, 06 Aug 2010 12:42:12 -0600 Grant Likely wrote: > > of_i8042_{kbd,aux}_irq needs to be exported > > Signed-off-by: Grant Likely > --- > > Stephen and Ben, this fixes up the build error in linux-next. If you prefer, > I can stuff this patch into my next-powerpc branch. Ben,

Re: [PATCH] powerpc: fix i8042 module build error

2010-08-06 Thread Grant Likely
On Fri, Aug 6, 2010 at 6:01 PM, Stephen Rothwell wrote: > Hi Grant, > > On Fri, 06 Aug 2010 12:42:12 -0600 Grant Likely > wrote: >> >> of_i8042_{kbd,aux}_irq needs to be exported >> >> Signed-off-by: Grant Likely >> --- >> >> Stephen and Ben, this fixes up the build error in linux-next.  If you

[git pull] powerpc allmodconfig build fix and missed 5200 audio drivers (Was: [PATCH] powerpc: fix i8042 module build error)

2010-08-06 Thread Grant Likely
Hi Ben, Here's the promised pull request: Let me know if this is okay, or if you would like to respin it. The 2 mpc5200 patches are in here (and not in my previous request) because of a breakdown in coordination between me and the ASoC folks. Turns out the (potentially) conflicting patches weren