>>> Hollis Blanchard 30.09.09 01:39 >>>
>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
>>> roel kluin 29.09.09 11:51 >>>
>On Tue, Sep 29, 2009 at 11:28 AM, 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 optimizat
> # size vmlinux
>text data bss dec hex filename
> 9812942 1982496 1105228 12900666 c4d93a vmlinux
... over kernel releases with pseries_defconfig:
text databss dec hex
2.6.32-rc1 9872090 1971184 1105236 12948
On Tue, Sep 29, 2009 at 2:43 PM, John Bonesio 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: Grant Likely
> S
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 */
> >-BUILD_BUG_ON(__builti
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
Signed-off-by: John Bonesio
---
This driver was originally written b
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 tl
Thus spake Joakim Tjernlund (joakim.tjernl...@transmode.se):
> Benjamin Herrenschmidt 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
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
---
diff --gi
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
---
diff --git
> -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 v
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
Benjamin Herrenschmidt 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 "correct" fix(un
On Tue, Sep 29, 2009 at 11:28 AM, 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 */
>>- BUILD_BUG_ON(__builtin_con
>>> 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(ty
Benjamin Herrenschmidt 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 "correct" fix(un
> 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
Benjamin Herrenschmidt 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
> > > unstable: som
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
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 re
20 matches
Mail list logo
