I've verified this patch can apply for galak/powerpc.git 'next' branch with no
change.
Best Regards,
Shaohui Xie
>-Original Message-
>From: Xie Shaohui-B21989
>Sent: Thursday, July 21, 2011 6:33 PM
>To: linuxppc-dev@lists.ozlabs.org
>Cc: Gala Kumar-B11780; mm-comm...@vger.kernel.org;
>-Original Message-
>From: Xie Shaohui-B21989
>Sent: Thursday, July 21, 2011 6:30 PM
>To: linuxppc-dev@lists.ozlabs.org
>Cc: Gala Kumar-B11780; Jiang Kai-B18973; Kumar Gala; Xie Shaohui-B21989
>Subject: [PATCH 3/4] powerpc/85xx: Merge PCI/PCI Express error management
>registers
>
>From: K
Add a newline to the panic messages in make_room. Also fix a
comment that suggested our chunk size is 4Mb. It's 1MB.
Signed-off-by: Anton Blanchard
---
Index: linux-powerpc/arch/powerpc/kernel/prom_init.c
===
--- linux-powerpc.orig
I have a box that fails in OF during boot with:
DEFAULT CATCH!, exception-handler=fff00400
at %SRR0: 49424d2c4c6f6768 %SRR1: 80004000b002
ie "IBM,Logh". OF got corrupted with a device tree string.
Looking at make_room and alloc_up, we claim the first chunk (1 MB)
but we never claim an
compatible in dts has been changed, so driver need to update accordingly.
Signed-off-by: Shaohui Xie
---
apply for http://git.kernel.org/pub/scm/linux/kernel/git/galak/powerpc.git
'next' branch.
drivers/edac/mpc85xx_edac.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
Hello,
Heiko Schocher wrote:
> Signed-off-by: Heiko Schocher
> cc: linux-net...@vger.kernel.org
> cc: Wolfgang Denk
> ---
> drivers/net/phy/Kconfig |5 ++
> drivers/net/phy/Makefile |1 +
> drivers/net/phy/amd79.c | 109
> ++
> 3 files cha
Hello,
Heiko Schocher wrote:
> Signed-off-by: Heiko Schocher
> cc: Grant Likely
> cc: devicetree-disc...@ozlabs.org
> cc: Wolfgang Denk
> cc: Wolfram Sang
> ---
> For this patchseries following patch is needed:
>
> http://patchwork.ozlabs.org/patch/91919/
>
> Grant? Do you have some comments
Hi Linus !
Here's the powerpc batch for this merge window (there might still be a
handful of small fixes coming later this week depending on my mood but
here's the bulk at least). There's a couple of trivial merge conflicts
with your tree, let me know if you prefer that I fix them myself.
No big
u64 is used rather than phys_addr_t to keep things simple, as
this is called from assembly code.
Update callers to pass a 64-bit address in r3/r4. Other unused
register assignments that were once parameters to machine_init
are dropped.
For FSL BookE, look up the physical address of the device tr
Commit af9eef3c7b1ed004c378c89b87642f4937337d50 caused cpu_setup to see
the_cpu_spec, rather than the source struct. However, on 32-bit, the
return value of identify_cpu was being used for feature fixups, and
identify_cpu was returning the source struct. So if cpu_setup patches
the feature bits,
Add a cast in case the caller passes in a different type, as it would
if mtspr/mtmsr were functions.
Previously, if a 64-bit type was passed in on 32-bit, GCC would bind the
constraint to a pair of registers, and would substitute the first register
in the pair in the asm code. This corresponds to
Capture more than twice as much text from the printk buffer, and
compress it to fit it in the lnx,oops-log NVRAM partition. You
can view the compressed text using the new (as of July 20) --unzip
option of the nvram command in the powerpc-utils package.
Signed-off-by: Jim Keniston
---
arch/powe
On Sat, 23 Jul 2011 01:45:53 +0400
Dmitry Eremin-Solenikov wrote:
> I see your point. I just wasn't thinking too much about ot-of-tree trees.
> My thought was that if someone updates the kernel, he can also update the dtb.
Sometimes there are firmware dependencies that make that difficult. And
Hi Ben:
On 07/24/2011 07:55 PM, Benjamin Herrenschmidt wrote:
> On Sun, 2011-07-24 at 11:18 -0600, David Ahern wrote:
>> On 07/20/2011 03:57 PM, David Ahern wrote:
>>> I am hoping someone familiar with PPC can help understand a panic that
>>> is generated when capturing callchains with context swi
[ a few minor fixes ]
The following changes since commit 50d2a4223bb875d1e3a7ee97d40dd03bf31ce1b7:
powerpc: Copy back TIF flags on return from softirq stack (2011-07-22
13:38:58 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/galak/powerpc.git ne
Hi All,
A problem was observed in gianfar driver when the interface MTU was modified to
a small value.
FYI Kernel Version : 2.6.32 on PPC.
Like if we change the interface mtu to say 100, ping traffic with size greater
than 450 is failing.
It was observed that packets ( ping requests) going ou
On Mon, 25 Jul 2011 09:23:38 +1000
Benjamin Herrenschmidt wrote:
> Hrm.. the faulting address is outside of the zImage. Odd.
>
> Can you try loading a plain vmlinux instead ? (feel free to strip it).
The plain unstripped vmlinux boots fine:
mb@maggie:~$ uname -a
Linux maggie 3.0.0 #3 PREEMPT Su
On Mon, 2011-07-25 at 12:33 +1000, Anton Blanchard wrote:
> Here are a set of ppc64 scheduler fixes that help with some
> multi node performance issues.
They look fine to me. I'll probably ping you when I'll rip out all that
SD_NODES_PER_DOMAIN crap for good, but until then I'm fine with you
fiddl
We have two identical definitions of RECLAIM_DISTANCE, looks like
the patch got applied twice. Remove one.
Signed-off-by: Anton Blanchard
---
Index: linux-2.6-work/arch/powerpc/include/asm/topology.h
===
--- linux-2.6-work.orig/arc
On big POWER7 boxes we see large amounts of CPU time in system
processes like workqueue and watchdog kernel threads.
We currently rebalance the entire machine each time a task goes
idle and this is very expensive on large machines. Disable newidle
balancing at the node level and rely on the schedu
The largest POWER7 boxes have 32 nodes. SD_NODES_PER_DOMAIN groups
nodes into chunks of 16 and adds a global balancing domain
(SD_ALLNODES) above it.
If we bump SD_NODES_PER_DOMAIN to 32, then we avoid this extra
level of balancing on our largest boxes.
Signed-off-by: Anton Blanchard
---
Index
We want to override the default value of SD_NODES_PER_DOMAIN on ppc64,
so move it into linux/topology.h.
Signed-off-by: Anton Blanchard
---
Index: linux-2.6-work/include/linux/topology.h
===
--- linux-2.6-work.orig/include/linux/to
When chasing a performance issue on ppc64, I noticed tasks
communicating via a pipe would often end up on different nodes.
It turns out SD_WAKE_AFFINE is not set in our node defition. Commit
9fcd18c9e63e (sched: re-tune balancing) enabled SD_WAKE_AFFINE
in the node definition for x86 and we need a
Here are a set of ppc64 scheduler fixes that help with some
multi node performance issues.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
The VPA, SLB shadow and DTL degistration functions do not need an
address, so simplify things and remove it.
Also cleanup pseries_kexec_cpu_down a bit by storing the cpu IDs
in local variables.
Signed-off-by: Anton Blanchard
---
Index: linux-powerpc/arch/powerpc/platforms/pseries/hotplug-cpu.c
Make the VPA, SLB shadow and DTL registration and deregistration
functions print consistent messages on error. I needed the firmware
error code while chasing a kexec bug but we weren't printing it.
Signed-off-by: Anton Blanchard
---
Index: linux-powerpc/arch/powerpc/platforms/pseries/kexec.c
===
Recent versions of firmware will fail to unmap the virtual processor
area if we have a dispatch trace log registered. This causes kexec
to fail.
If a trace log is registered this patch unregisters it before the
SLB shadow and virtual processor areas, fixing the problem.
The address argument is ig
Here are a few pseries kexec fixes after testing on a recent version
version.
Anton
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
28 matches
Mail list logo
