Yeah, I agree. This needs a better description. I only know what's
going
on because I was there for the start of the discussion.
But just to be sure, this is what I think is happening.
When we add "-pg" to gcc, it automatically causes frame pointers to be
used.
Nope, it does no such thing.
Hannes Hering wrote:
> pref = skb_array[x];
> - prefetchw(pref);
> - prefetchw(pref + EHEA_CACHE_LINE);
> + if (pref) {
> + prefetchw(pref);
> + prefetchw(pref + EHEA_CACHE_LINE);
Ummm... Is prefetch() or prefetchw() faulting?
David
___
On May 4, 2009, at 5:25 PM, Morrison, Tom wrote:
I have both a MPC8548 SBC and MPC8572 system that are running
different flavors of the
same Linux – 2.6.23.
I explicitly am turning it on very early on. Later, I have an
application that is compiled
with SPE instructions (e.g.: evstdd) , and
On Tuesday 05 May 2009 11:11:27 David Howells wrote:
> Hannes Hering wrote:
>
> > pref = skb_array[x];
> > - prefetchw(pref);
> > - prefetchw(pref + EHEA_CACHE_LINE);
> > + if (pref) {
> > + prefetchw(pref);
> > + prefetchw(pref + EHEA_CACHE_LINE);
>
> Ummm... Is p
On Apr 30, 2009, at 9:50 AM, Michael Ellerman wrote:
On Thu, 2009-04-30 at 09:18 -0500, Kumar Gala wrote:
On Apr 30, 2009, at 8:49 AM, Michael Ellerman wrote:
On Thu, 2009-04-30 at 08:09 -0500, Kumar Gala wrote:
We shouldn't be accessing sysdata directly. In the future we might
have
sysdat
Hi all,
Target : PowerPC, Virtex-440 Generic
Serial port : Xilinx 16550 Uart ( depends on OF_PLATFORM)
Further investigation of KGDBOC on PowerPC shows that kgdboc hangs at :
In file : arch/powerpc/include/asm/kgdb.h
*static inline void* arch_kgdb_breakpoint(*void*)
{
*asm*(*".long 0x7d
Jeremy Kerr wrote on 05/05/2009 02:57:18 AM:
> Hi Gerhard,
Jeremy, thanks for your comments
>
> > This is for QS21. The following patch allocates pages only from
> > the specified node, moves the ptcal area into the middle of the
> > allocated page to avoid potential prefetch problems and prin
We shouldn't directly access sysdata to get the device node. We should
be calling pci_device_to_OF_node().
Signed-off-by: Kumar Gala
---
arch/powerpc/platforms/iseries/pci.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/powerpc/platforms/iseries/pci.c
b/a
* Removed building setup-irq on ppc32, we don't use it anymore
* Remove duplicate prototype for setup_grackle() code that needs it
gets it from
* Removed gratuitous pci_io_size type differences between ppc32/ppc64
Signed-off-by: Kumar Gala
---
arch/powerpc/include/asm/pci-bridge.h |6
The pcnet32 driver has had in its device id table for some time a match
against the "broken" vendor ID. No need to fake out the vendor ID
with an explicit fixup.
Signed-off-by: Kumar Gala
---
arch/powerpc/kernel/pci_32.c | 11 ---
arch/powerpc/kernel/pci_64.c | 10 --
2 file
Hannes Hering wrote:
> this is an ehea driver problem, which is occuring when the receive queue runs
> empty. The faulting code is more specifically the following line:
>
> pref = (skb_array[x]->data);
In that case, you might want to move the prefetchw() calls in the following:
Ben,
Here are various pci related changes for 2.6.31 that can look at going
into your test tree to see if they break anyone. It would be nice if this
could get some testing on pseries by one of you guys as I have no access
to such HW.
- k
Please pull from 'pci' branch of
master.kernel.
Hi Kumar/Michael...
Sorry, I really didn't explain myself very well...
The Problem (answer to Michael):
We started using a new compiler that upon -O2 optimization - added
heavy SPE related instructions into our applications (where the older
compiler might not use
On Tue, May 5, 2009 at 5:28 PM, Jason Wessel wrote:
> srikanth krishnakar wrote:
> > Hi all,
> >
> > Target : PowerPC, Virtex-440 Generic
> > Serial port : Xilinx 16550 Uart ( depends on OF_PLATFORM)
> >
> > Further investigation of KGDBOC on PowerPC shows that kgdboc hangs at :
> >
> > In file :
On Tue, 2009-05-05 at 09:56 +0200, Segher Boessenkool wrote:
> > Yeah, I agree. This needs a better description. I only know what's
> > going
> > on because I was there for the start of the discussion.
> >
> > But just to be sure, this is what I think is happening.
> >
> > When we add "-pg" to g
On Tuesday 05 May 2009 14:19:54 David Howells wrote:
> In that case, you might want to move the prefetchw() calls in the following:
>
> pref = skb_array[x];
> - prefetchw(pref);
> - prefetchw(pref + EHEA_CACHE_LINE);
> + if (pref) {
> +
When we add "-pg" to gcc, it automatically causes frame pointers
to be
used.
Nope, it does no such thing.
Well, mcount is expected to be able to get to not just who called
mcount, but also the parent of that function. The way mcount is
implemented does not let you do that. If mcount was the
Landau, Bracha wrote:
I've upgraded to the latest kernel (2.6.29), and after updating the
configuration the cuImage did boot.
What's the difference between the address for the early debug console for
cuImage and uImage + blob?
The address is wherever the previous driver (u-boot or bootwrapper
===
This is for QS21. The following patch allocates pages only from
the specified node, moves the ptcal area into the middle of the
allocated page to avoid potential prefetch problems and prints
the address of the ptcal area to fac
Hello,
I have a Kernel 2.6.24 running on a custom board based on mpc8313erdb.
My filesystem is composed by a read-only squashfs and a read-write jffs2
filesystems. A unionfs is used to unificate the filesystems.
Like you know, when a file on my read-only squasfs is modified such file
is copied to
On Mon, May 04, 2009 at 10:23:50PM -0700, Sauce.Cheng wrote:
> i want to mapping FIFO memory to bank 3 by configure br3 and or3
> the boot info as following.
>
> in my code, i have mapped FIFO to 0xD000, then i red the value from this
> address.
>
> the prompts as following
>
> there is som
The receive interrupt routine checks the wrong register if the
receive fifo is empty. Further an explicit interrupt acknowledge
write is introduced. In some circumstances another interrupt was
issued.
Signed-off-by: Benjamin Krill
---
drivers/serial/nwpserial.c |4 +++-
1 files changed, 3 in
On Tue, May 5, 2009 at 2:11 PM, Benjamin Krill wrote:
> The receive interrupt routine checks the wrong register if the
> receive fifo is empty. Further an explicit interrupt acknowledge
> write is introduced. In some circumstances another interrupt was
> issued.
The one-line summary of your patch
On Mon, May 4, 2009 at 1:55 PM, Judd Gilbert wrote:
> I have a driver which maps some kernel allocated memory to user space which
> works, and now I am trying to set that memory non-cacheable, on a power PC
> using the Denx ELDK (linux-2.6.24) on a PPC460ex.
Because of the way the kernel maps mai
On May 5, 2009, at 7:56 AM, Morrison, Tom wrote:
Hi Kumar/Michael...
Sorry, I really didn't explain myself very well...
The Problem (answer to Michael):
We started using a new compiler that upon -O2 optimization - added
heavy SPE related instructions into our
The macro spin_event_timeout() takes a condition and timeout value
(in microseconds) as parameters. It spins until either the condition is true
or the timeout expires. It returns the result of the condition when the loop
was terminated.
This primary purpose of this macro is to poll on a hardware
On Tue, May 05, 2009 at 04:16:45PM -0500, Timur Tabi wrote:
>On Mon, May 4, 2009 at 1:55 PM, Judd Gilbert wrote:
>> I have a driver which maps some kernel allocated memory to user space which
>> works, and now I am trying to set that memory non-cacheable, on a power PC
>> using the Denx ELDK (linu
On Tue, May 05, 2009 at 02:24:04PM -0500, Timur Tabi wrote:
>On Tue, May 5, 2009 at 2:11 PM, Benjamin Krill wrote:
>> The receive interrupt routine checks the wrong register if the
>> receive fifo is empty. Further an explicit interrupt acknowledge
>> write is introduced. In some circumstances ano
On Tue, 2009-05-05 at 15:51 +0200, Segher Boessenkool wrote:
> >>> When we add "-pg" to gcc, it automatically causes frame pointers
> >>> to be
> >>> used.
> >>
> >> Nope, it does no such thing.
> >
> > Well, mcount is expected to be able to get to not just who called
> > mcount, but also the pa
> Hi Kumar/Michael...
>
> Sorry, I really didn't explain myself very well...
>
> The Problem (answer to Michael):
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> =3D=3D=3D=3D=3D=3D=3D
> We started using a new compiler that upon -O2 optimization - added
> heavy SPE
Ok...taken out...
>> -Original Message-
>> From: Kumar Gala [mailto:ga...@kernel.crashing.org]
>> Sent: Tuesday, May 05, 2009 5:18 PM
>> To: Morrison, Tom
>> Cc: linuxppc-dev@ozlabs.org; Michael Neuling
>> Subject: Re: MSR_SPE - being turned off...
>>
>>
>> On May 5, 2009, at 7:56 AM, Mo
The test case we found is under 'extreme' duress
(intense loading on an MPC8572)...with many applications
using A LOT of SPE instructions...
If you look at the context switch code (in latest code entry_32.S),
I believe the context switch performs a SAVE_NVGPR() - which in our
interpre
On Tue, 5 May 2009 16:53:05 -0500
"Timur Tabi" wrote:
> The macro spin_event_timeout() takes a condition and timeout value
> (in microseconds) as parameters. It spins until either the condition
> is true or the timeout expires. It returns the result of the
> condition when the loop was termina
On May 5, 2009, at 7:42 PM, Morrison, Tom wrote:
The test case we found is under 'extreme' duress
(intense loading on an MPC8572)...with many applications
using A LOT of SPE instructions...
If you look at the context switch code (in latest code entry_32.S),
I believe the context swit
34 matches
Mail list logo
