On Friday 20 June 2008 16:36:20 you wrote:
I have a set of patches that I will be submitting later today that
adds the generic board support without removing ADS. So I would
prefer for you to just submit a device tree file for your board.
Ok, thanks. I'll check your patches, fix our DT and
If we set the SPE MSR bit in save_user_regs we can blow away the VEC
bit. This will never happen in reality (VMX and SPE will never be in
the same processor as their opcodes overlap), but it looks bad. Also
when we add VSX here in a later patch, we can hit two of these at the
same time.
The following set of patches adds Vector Scalar Extentions (VSX)
support for POWER7. Includes context switch, ptrace and signals support.
Signed-off-by: Michael Neuling [EMAIL PROTECTED]
---
Paulus: please consider for your 2.6.27 tree.
Updates this post
- Fixed ptrace 32 error noticed by
We are going to change where the floating point registers are stored
in the thread_struct, so in preparation add some macros to access the
floating point registers. Update all code to use these new macros.
Signed-off-by: Michael Neuling [EMAIL PROTECTED]
---
arch/powerpc/kernel/align.c |
The layout of the new VSR registers and how they overlap on top of the
legacy FPR and VR registers is:
VSR doubleword 0 VSR doubleword 1
VSR[0] | FPR[0]|
Add a VSX CPU feature. Also add code to detect if VSX is available
from the device tree.
Signed-off-by: Michael Neuling [EMAIL PROTECTED]
Signed-off-by: Joel Schopp [EMAIL PROTECTED]
---
arch/powerpc/kernel/prom.c |4
include/asm-powerpc/cputable.h | 15 ++-
2 files
This patch extends the floating point save and restore code to use the
VSX load/stores when VSX is available. This will make FP context
save/restore marginally slower on FP only code, when VSX is available,
as it has to load/store 128bits rather than just 64bits.
Mixing FP, VMX and VSX code will
Add CONFIG_VSX config build option. Must compile with POWER4, FPU and ALTIVEC.
Signed-off-by: Michael Neuling [EMAIL PROTECTED]
---
arch/powerpc/platforms/Kconfig.cputype | 16
1 file changed, 16 insertions(+)
Index: linux-2.6-ozlabs/arch/powerpc/platforms/Kconfig.cputype
Make load_up_fpu and load_up_altivec callable so they can be reused by
the VSX code.
Signed-off-by: Michael Neuling [EMAIL PROTECTED]
---
arch/powerpc/kernel/fpu.S|2 +-
arch/powerpc/kernel/head_32.S|6 --
arch/powerpc/kernel/head_64.S| 10 +++---
This adds the macros for the VSX load/store instruction as most
binutils are not going to support this for a while.
Also add VSX register save/restore macros and vsr[0-63] register definitions.
Signed-off-by: Michael Neuling [EMAIL PROTECTED]
---
include/asm-powerpc/ppc_asm.h | 127
Currently we set the start of the .text section to be 4Mb for pSeries.
In situations where the zImage is 8Mb we'll fail to boot (due to
overlapping with OF). Move .text in a zImage from 4MB to 64MB (well past OF).
We still will not be able to load large zImage unless we also move OF,
to that
On Mon, Jun 23, 2008 at 06:13:23PM +1000, Tony Breeds wrote:
Currently we set the start of the .text section to be 4Mb for pSeries.
In situations where the zImage is 8Mb we'll fail to boot (due to
overlapping with OF). Move .text in a zImage from 4MB to 64MB (well past OF).
We still will
Hi Sanya,
I have no idea how important unaligned or uncacheable
copy perf is for Cell Linux. My experience is from Mac
OS X for PPC, where we used dcbz in a general-purpose
memcpy but were forced to pull that optimization because
of the detrimental perf effect on important applications.
On Mon, Jun 23, 2008 at 06:13:23PM +1000, Tony Breeds wrote:
Currently we set the start of the .text section to be 4Mb for pSeries.
In situations where the zImage is 8Mb we'll fail to boot (due to
overlapping with OF). Move .text in a zImage from 4MB to 64MB (well past OF).
We still will
I have a custom config to build a kernel which runs on JS21/QS21/QS22.
Starting with 2.6.26-rc1 that fails on JS21 (with SLOF). Bisecting lead
me to the following commit:
commit 366234f657879aeb7a1e2ca582f2f24f3fae9269
Author: Kumar Gala [EMAIL PROTECTED]
Date: Wed Apr 16 05:52:28 2008
On Mon, 2008-06-23 at 11:30 +0200, Adrian Reber wrote:
On Mon, Jun 23, 2008 at 06:13:23PM +1000, Tony Breeds wrote:
Currently we set the start of the .text section to be 4Mb for pSeries.
In situations where the zImage is 8Mb we'll fail to boot (due to
overlapping with OF). Move .text in a
On Mon, 2008-06-23 at 11:45 +0200, Adrian Reber wrote:
I have a custom config to build a kernel which runs on JS21/QS21/QS22.
Starting with 2.6.26-rc1 that fails on JS21 (with SLOF). Bisecting lead
me to the following commit:
commit 366234f657879aeb7a1e2ca582f2f24f3fae9269
Author: Kumar
On Mon, Jun 16, 2008 at 11:10:40AM -0500, Kim Phillips wrote:
Signed-off-by: Kim Phillips [EMAIL PROTECTED]
I've merged these patches into the original changeset. Thanks!
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page:
On Mon, 23 Jun 2008, Gunnar von Boehn wrote:
The problem is that the dcbz will generate the alignment exception
regardless of whether the data is actually unaligned or not.
Once you're on that code path, performance can't be good, can it?
In which case will DCBZ create an aligned
On Mon, 2008-06-23 at 18:13 +1000, Tony Breeds wrote:
Currently we set the start of the .text section to be 4Mb for pSeries.
In situations where the zImage is 8Mb we'll fail to boot (due to
overlapping with OF). Move .text in a zImage from 4MB to 64MB (well past OF).
...
diff --git
Hi guys,
I keep getting export errors when building kernels, a conflict between
arch/powerpc/lib/rheap.c:rh_init() and drivers/dm/dm-region_hash.c:rh_init()
- in the event you want to use BestComm, MPC8610 DIU or other features
*and* a RAID algorithm, which subsystem would be best to patch away
Matt Sealey wrote:
I was thinking of renaming the dm hash one to rh_hash_init() and then I
thought, maybe rh_heap_init() is better. Then I thought, why have rh in
both places, why not rename the entire API (rheap_ and rhash_) in both
cases?
I'm okay with renaming the rh_xxx calls in rheap.c
From: Sathya Narayanan [EMAIL PROTECTED]
Short packets has to be discarded by the driver. So this patch addresses the
issue of discarding the short packets of size lesser then ethernet header
size.
Signed-off-by: Sathya Narayanan [EMAIL PROTECTED]
Signed-off-by: Stefan Roese [EMAIL PROTECTED]
From: Sathya Narayanan [EMAIL PROTECTED]
The descriptor pointers were not initialized to NIL values, so it was
poiniting to some random addresses which was completely invalid. This
fix takes care of initializing the descriptor to NIL values and clearing
the valid descriptors on clean ring
From: Sathya Narayanan [EMAIL PROTECTED]
This patch addresses the memory leak happenning in drivers transmit queue
under heavy load condition. Once the transmit queue becomes full, driver
does an automatic wrapup of queue. During which the untransmitted SKB's are
lost without getting freed up.
i am working with a board of mpc8313 using default mpc8313erdb.dts.
But i do not know how can i correctly use DMA to transport data from memory
to a PCI device.
i tryed this
{
.
request_irq(IRQ,);
request_dma(.);
}
In request_irq() , i do not know what is the
On Jun 23, 2008, at 2:38 AM, Michael Neuling wrote:
If we set the SPE MSR bit in save_user_regs we can blow away the VEC
bit. This will never happen in reality (VMX and SPE will never be in
the same processor as their opcodes overlap), but it looks bad. Also
when we add VSX here in a later
On Jun 21, 2008, at 7:20 PM, Benjamin Herrenschmidt wrote:
On Sat, 2008-06-21 at 11:07 -0500, Kumar Gala wrote:
Remind me why we want to do that ? ie. can't we just use lwsync
unconditionally ? It's supposed to degrade to sync on CPUs that
don't
support it, or is that broken on some parts
Hi,
I'm in the process of porting Linux to one of our boards based on an
8641D. Some of the interrupts of on-board devices are dealt with by a
custom interrupt controller in one of the onboard FPGAs, which cascades
into the 8641D's mpic. I'm trying to write a driver for it.
Looking at examples
On Mon, Jun 23, 2008 at 03:00:35PM +0100, Welch, Martyn (GE EntSol, Intelligent
Platforms) wrote:
I'm in the process of porting Linux to one of our boards based on an
8641D. Some of the interrupts of on-board devices are dealt with by a
custom interrupt controller in one of the onboard FPGAs,
On Tue, Jun 10, 2008 at 10:21:25AM +1000, Stephen Rothwell wrote:
Hi Adrian,
On Tue, 10 Jun 2008 01:23:12 +0300 Adrian Bunk [EMAIL PROTECTED] wrote:
+++ b/drivers/macintosh/adbhid.c
@@ -75,7 +75,7 @@ static struct notifier_block adbhid_adb_notifier = {
#define ADB_KEY_POWER_OLD 0x7e
This patch contains the following cleanups for the asm/ptrace.h
userspace headers:
- include/asm-generic/Kbuild.asm already lists ptrace.h, remove
the superfluous listings in the Kbuild files of the following
architectures:
- cris
- frv
- powerpc
- x86
- don't expose function
asm/asm-compat.h doesn't seem to be intended for userspace usage.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
include/asm-powerpc/Kbuild |1 -
include/asm-powerpc/cputable.h |5 +++--
2 files changed, 3 insertions(+), 3 deletions(-)
4c78f2fc562d3aae525c8f62706a80479228c50e
This patch makes asm/elf.h export less non-userspace stuff to userspace.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
include/asm-powerpc/elf.h | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
6e868802e4b350a9dac071044b7cf52af7404134 diff --git
From: Julia Lawall [EMAIL PROTECTED]
This patch makes two changes:
* As noted by Akinobu Mita in patch
b1fceac2b9e04d278316b2faddf276015fc06e3b, alloc_bootmem never returns NULL
and always returns a zeroed region of memory. Thus the error checking code
and memset after the call to alloc_bootmem
On Mon, 23 Jun 2008, Adrian Bunk wrote:
On Tue, Jun 10, 2008 at 10:21:25AM +1000, Stephen Rothwell wrote:
On Tue, 10 Jun 2008 01:23:12 +0300 Adrian Bunk [EMAIL PROTECTED] wrote:
+++ b/drivers/macintosh/adbhid.c
@@ -75,7 +75,7 @@ static struct notifier_block adbhid_adb_notifier = {
From: Sathya Narayanan [EMAIL PROTECTED]
The descriptor pointers were not initialized to NIL values, so it was
poiniting to some random addresses which was completely invalid. This
fix takes care of initializing the descriptor to NIL values and clearing
the valid descriptors on clean ring
On Mon, 23 Jun 2008 10:28:53 -0600
John Linn [EMAIL PROTECTED] wrote:
This is an early patch against the mainline that I wanted to start
getting comments on.
I would appreciate any feedback.
I already see a few things that I need to look into myself.
1.I'm not sure why we need to
Fixed patch formatting.
Enable ibmveth for Cooperative Memory Overcommitment (CMO). For this driver
it means calculating a desired amount of IO memory based on the current MTU
and updating this value with the bus when MTU changes occur. Because DMA
mappings can fail, we have added a bounce
From: Santiago Leon [EMAIL PROTECTED]
Fixed patch formatting.
Activates larger rx buffer pools when the MTU is changed to a larger
value. This patch de-activates the large rx buffer pools when the MTU
changes to a smaller value.
Signed-off-by: Santiago Leon [EMAIL PROTECTED]
Signed-off-by:
ok, I queued this for 2.6.27. thanks everyone
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
* Stephen Rothwell ([EMAIL PROTECTED]) wrote:
Hi Robert,
Firstly, can all this new stuff be ifdef'ed out if not needed as the
vio infrastructure is also used on legacy iSeries and this adds quite a
bit of stuff that won't ever be used there.
I've changed the patch to ifdef out CMO for
From: Robert Jennings [EMAIL PROTECTED]
Enable bus level entitled memory accounting for Cooperative Memory
Overcommitment (CMO) environments. The normal code path should not
be affected.
The following changes are made that the VIO bus layer for CMO:
* add IO memory accounting per device
diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
index 3934e26..94adfe1 100644
--- a/arch/powerpc/Kconfig
+++ b/arch/powerpc/Kconfig
@@ -483,6 +483,81 @@ config SECCOMP
If unsure, say Y. Only embedded should say N here.
+config WANT_DEVICE_TREE
+ bool
+
Thanks for the comments Josh.
I commented on the others that Stephen didn't comment on.
diff --git a/arch/powerpc/boot/io.h b/arch/powerpc/boot/io.h
index ccaedae..ec57ec9 100644
--- a/arch/powerpc/boot/io.h
+++ b/arch/powerpc/boot/io.h
@@ -99,4 +99,11 @@ static inline void barrier(void)
On Mon, 2008-06-23 at 14:54 +0200, Stefan Roese wrote:
From: Sathya Narayanan [EMAIL PROTECTED]
The descriptor pointers were not initialized to NIL values, so it was
poiniting to some random addresses which was completely invalid. This
fix takes care of initializing the descriptor to NIL
On Mon, 2008-06-23 at 14:55 +0200, Stefan Roese wrote:
From: Sathya Narayanan [EMAIL PROTECTED]
Short packets has to be discarded by the driver. So this patch addresses the
issue of discarding the short packets of size lesser then ethernet header
size.
You are freeing the skb, why ?
On Mon, 2008-06-23 at 14:55 +0200, Stefan Roese wrote:
From: Sathya Narayanan [EMAIL PROTECTED]
This patch addresses the memory leak happenning in drivers transmit queue
under heavy load condition. Once the transmit queue becomes full, driver
does an automatic wrapup of queue. During which
Gunnar von Boehn writes:
Interesting points.
Can you help me to understand where the negative effect of DCBZ does come
from?
In my experience, dcbz slows down the hot-cache case because it adds a
few cycles to the execution time of the inner loop, and on most 64-bit
PowerPC implementations,
On Mon, 23 Jun 2008 20:46:57 +0300 Adrian Bunk [EMAIL PROTECTED] wrote:
On Tue, Jun 10, 2008 at 10:21:25AM +1000, Stephen Rothwell wrote:
Hi Adrian,
On Tue, 10 Jun 2008 01:23:12 +0300 Adrian Bunk [EMAIL PROTECTED] wrote:
+++ b/drivers/macintosh/adbhid.c
@@ -75,7 +75,7 @@ static
Hi Adrian,
Adrian Bunk wrote:
This patch contains the following cleanups for the asm/ptrace.h
userspace headers:
- include/asm-generic/Kbuild.asm already lists ptrace.h, remove
the superfluous listings in the Kbuild files of the following
architectures:
- cris
- frv
- powerpc
- x86
Thanks a lot for answer my question.
But i am newhand and not very clear about it.
Do you mean:
1. in this case i do not need to include DMA when i make menuconfig ?
The path is Device Drivers-DMA.
2. in this case i do not need add any DMA information in mpc8313erdb.dts?
Now i am reading
This patch adds a testcase for the /include/ directive. It assembles
a sample dts file with many /include/ directives at a variety of
different lexical / grammatical contexts.
Signed-off-by: David Gibson [EMAIL PROTECTED]
Index: dtc/tests/include0.dts
We currently have a few routines for patching code in asm/system.h, because
they didn't fit anywhere else. I'd like to clean them up a little and add
some more, so first move them into a dedicated C file - they don't need to
be inlined.
While we're moving the code, drop create_function_call(),
Currently create_branch() creates a branch instruction for you, and patches
it into the call site. In some circumstances it would be nice to be able to
create the instruction and patch it later, and also some code might want
to check for errors in the branch creation before doing the patching. A
If you pass a target value to create_branch() which is more than 32MB - 4,
or - 32MB away from the branch site, then it's impossible to create an
immediate branch. The current code doesn't check, which will lead to us
creating a branch to somewhere else - which is bad.
For code that cares to
Because function pointers point to different things on 32-bit vs 64-bit,
add a macro that deals with dereferencing the OPD on 64-bit. The soon to
be merged ftrace wants this, as well as other code I am working on.
Signed-off-by: Michael Ellerman [EMAIL PROTECTED]
---
This commit adds some new routines for patching code, they will be used
in a following commit.
Signed-off-by: Michael Ellerman [EMAIL PROTECTED]
---
arch/powerpc/lib/code-patching.c| 107 +++
include/asm-powerpc/code-patching.h |8 +++
2 files changed,
Add tests of the existing code patching routines, as well as the new
routines added in the last commit. The self-tests are run late in boot
when CONFIG_CODE_PATCHING_SELFTEST=y, which depends on DEBUG_KERNEL=y.
Signed-off-by: Michael Ellerman [EMAIL PROTECTED]
---
arch/powerpc/Kconfig.debug
A bunch of code has hard-coded the value for a nop instruction, it
would be nice to have a #define for it.
Signed-off-by: Michael Ellerman [EMAIL PROTECTED]
---
arch/powerpc/kernel/cputable.c |3 ++-
arch/powerpc/kernel/crash_dump.c|2 +-
arch/powerpc/kernel/module_64.c |
The logic to patch CPU feature sections lives in cputable.c, but these days
it's used for CPU features as well as firmware features. Move it into
it's own file for neatness and as preparation for some additions.
While we're moving the code, we pull the loop body logic into a separate
routine, and
The CPU and firmware feature fixup macros are currently spread across
three files, firmware.h, cputable.h and asm-compat.h. Consolidate them
into their own file, feature-fixups.h
Signed-off-by: Michael Ellerman [EMAIL PROTECTED]
---
include/asm-powerpc/asm-compat.h | 51 -
Currentl we have three versions of MAKE_FTR_SECTION_ENTRY(), the macro that
generates a feature section entry. There is 64bit version, a 32bit version
and version for 32bit code built with a 64bit kernel.
Rather than triplicating (?) the MAKE_FTR_SECTION_ENTRY() logic, we can
move the 64bit/32bit
The current feature section logic only supports nop'ing out code, this means
if you want to choose at runtime between instruction sequences, one or both
cases will have to execute the nop'ed out contents of the other section, eg:
BEGIN_FTR_SECTION
or 1,1,1
END_FTR_SECTION_IFSET(FOO)
This patch adds the logic to patch alternative sections. This is fairly
straight forward, except for branches. Relative branches that jump from
inside the else section to outside of it, need to be translated as they're
moved, otherwise they will jump to the wrong location.
Signed-off-by: Michael
This commit adds tests of the feature fixup code, they are run during
boot if CONFIG_FTR_FIXUP_SELFTEST=y. Some of the tests manually invoke
the patching routines to check their behaviour, and others use the
macros and so are patched during the normal patching done during boot.
Because we have
Use an alternative feature section in _switch. There are three cases
handled here, either we don't have an SLB, in which case we jump over the
entire code section, or if we do we either do or don't have 1TB segments.
Boot tested on Power3, Power5 and Power5+.
Signed-off-by: Michael Ellerman
On Mon, 23 Jun 2008 15:30:35 -0600
John Linn [EMAIL PROTECTED] wrote:
+ *
+ * Copyright 2007 IBM Corporation
+ * Based on cuboot-83xx.c, which is:
+ * Copyright (c) 2007 Freescale Semiconductor, Inc.
+ *
+ * This program is free software; you can redistribute it and/or
modify
it
Finalizing device tree... using OF tree (promptr=0e1004c4)
( 700 ) Program Exception [ e1004c4 ]
The program check exception happens at 0xe1004c4 ? That looks like the
OF entry point (promptr)... could it be possible that it got corrupted
somewhat ? The only thing I see above there would be
On Tue, May 13, 2008 at 12:25:27PM -0500, Jon Tollefson wrote:
Instead of using the variable mmu_huge_psize to keep track of the huge
page size we use an array of MMU_PAGE_* values. For each supported
huge page size we need to know the hugepte_shift value and have a
pgtable_cache. The hstate
Currently we set the start of the .text section to be 4Mb for pSeries.
In situations where the zImage is 8Mb we'll fail to boot (due to
overlapping with OF). Move .text in a zImage from 4MB to 64MB (well past OF).
We still will not be able to load large zImage unless we also move OF,
to that
On Mon, Jun 23, 2008 at 08:48:09PM +0300, Adrian Bunk wrote:
This patch contains the following cleanups for the asm/ptrace.h
userspace headers:
- include/asm-generic/Kbuild.asm already lists ptrace.h, remove
the superfluous listings in the Kbuild files of the following
architectures:
On Mon, Jun 23, 2008 at 08:48:09PM +0300, Adrian Bunk wrote:
This patch contains the following cleanups for the asm/ptrace.h
userspace headers:
- include/asm-generic/Kbuild.asm already lists ptrace.h, remove
the superfluous listings in the Kbuild files of the following
architectures:
I use this in 8313erdb.dts, but can not find DMA info in
/proc/interrupts.why?
[EMAIL PROTECTED] {
#address-cells = 1;
#size-cells = 1;
compatible = fsl,elo-dma;
cell-index = 0;
74 matches
Mail list logo
