Thus spake Benjamin Herrenschmidt (b...@kernel.crashing.org):
On Thu, 2009-09-24 at 18:35 -0700, Rex Feany wrote:
Then I can boot and get to a shell, but userspace is slow. 8 seconds
to mount
/proc (vs. less then a second using my old kernel)! Maybe this is an
unrelated issue?
On 9/28/09 5:41 PM, John Linn wrote:
-Original Message-
From: Richard Röjfors [mailto:richard.rojf...@mocean-labs.com]
Sent: Monday, September 28, 2009 8:22 AM
To: spi-devel-gene...@lists.sourceforge.net
Cc: linuxppc-...@ozlabs.org; dbrown...@users.sourceforge.net; Andrew Morton;
On Mon, 2009-09-28 at 18:21 -0700, Rex Feany wrote:
It's going to be hard for me to get that right since I don't really
know what's going on with the core here, but I suppose if we get it
moving along with extra tlb invalidations, that should be good enough
until somebody who really knows
On Tue, 2009-09-29 at 08:26 +0200, Joakim Tjernlund wrote:
I've tried sticking tlbil_va() in those places, nothing seems to
help.
In some cases userspace is slow, in other cases userspace is faster
and
unstable: sometimes commands hang, sometimes I am able to ctrl-c and
and kill it,
Benjamin Herrenschmidt b...@kernel.crashing.org wrote on 29/09/2009 09:07:37:
On Tue, 2009-09-29 at 08:26 +0200, Joakim Tjernlund wrote:
I've tried sticking tlbil_va() in those places, nothing seems to
help.
In some cases userspace is slow, in other cases userspace is faster
and
hmm, yes. You do get this and mysterious SEGV if you hit the but so does
other bugs too so this is probably due to missing invalidation.
I suspect that something like below will fix the problem and
is the correct fix(untested, not even compiled):
Ok but do we also still have to worry about
Benjamin Herrenschmidt b...@kernel.crashing.org wrote on 29/09/2009 10:16:38:
hmm, yes. You do get this and mysterious SEGV if you hit the but so does
other bugs too so this is probably due to missing invalidation.
I suspect that something like below will fix the problem and
is the
Hollis Blanchard 09/29/09 2:00 AM
First, I think there is a real bug here, and the code should read like
this (to match the comment):
/* type has to be known at build time for optimization */
-BUILD_BUG_ON(__builtin_constant_p(type));
+BUILD_BUG_ON(!__builtin_constant_p(type));
On Tue, Sep 29, 2009 at 11:28 AM, Jan Beulich jbeul...@novell.com wrote:
Hollis Blanchard 09/29/09 2:00 AM
First, I think there is a real bug here, and the code should read like
this (to match the comment):
/* type has to be known at build time for optimization */
-
Benjamin Herrenschmidt b...@kernel.crashing.org wrote on 29/09/2009 10:16:38:
hmm, yes. You do get this and mysterious SEGV if you hit the but so does
other bugs too so this is probably due to missing invalidation.
I suspect that something like below will fix the problem and
is the
When running Active Memory Sharing, the Collaborative Memory Manager (CMM)
may mark some pages as loaned with the hypervisor. Periodically, the
CMM will query the hypervisor for a loan request, which is a single signed
value. When kexec'ing into a kdump kernel, the CMM driver in the kdump
kernel
-Original Message-
From: Richard Röjfors [mailto:richard.rojf...@mocean-labs.com]
Sent: Tuesday, September 29, 2009 12:35 AM
To: John Linn
Cc: spi-devel-gene...@lists.sourceforge.net; linuxppc-...@ozlabs.org;
dbrown...@users.sourceforge.net; Andrew Morton
Subject: Re: [PATCH v4]
We need to align before the output section. Having the align inside
the output section causes the linker to put some filler in there,
which makes it a non-empty section, but this section isn't assigned to
a segment so you get a warning from the linker.
Signed-off-by: Sean MacLennan
We need to align before the output section. Having the align inside
the output section causes the linker to put some filler in there,
which makes it a non-empty section, but this section isn't assigned to
a segment so you get a warning from the linker.
Signed-off-by: Sean MacLennan
Thus spake Joakim Tjernlund (joakim.tjernl...@transmode.se):
Benjamin Herrenschmidt b...@kernel.crashing.org wrote on 29/09/2009
10:16:38:
hmm, yes. You do get this and mysterious SEGV if you hit the but so does
other bugs too so this is probably due to missing invalidation.
I
Thus spake Benjamin Herrenschmidt (b...@kernel.crashing.org):
On Mon, 2009-09-28 at 18:21 -0700, Rex Feany wrote:
It's going to be hard for me to get that right since I don't really
know what's going on with the core here, but I suppose if we get it
moving along with extra tlb
This is a driver for the FIFO device on the LocalPlus bus on an mpc5200 system.
The driver supports programmed I/O through the FIFO as well as setting up DMA
via the BestComm engine through the FIFO.
Signed-off-by: Grant Likely grant.lik...@secretlab.ca
Signed-off-by: John Bonesio
On Tue, 2009-09-29 at 10:28 +0100, Jan Beulich wrote:
Hollis Blanchard 09/29/09 2:00 AM
First, I think there is a real bug here, and the code should read like
this (to match the comment):
/* type has to be known at build time for optimization */
-
On Tue, Sep 29, 2009 at 2:43 PM, John Bonesio bo...@secretlab.ca wrote:
This is a driver for the FIFO device on the LocalPlus bus on an mpc5200
system.
The driver supports programmed I/O through the FIFO as well as setting up DMA
via the BestComm engine through the FIFO.
Signed-off-by:
19 matches
Mail list logo
