[PATCH, RT, RFC] Hacks allowing -rt to run on POWER7 / Powerpc.
We've been seeing some issues with userspace randomly SIGSEGV'ing while
running the -RT kernels on POWER7 based systems. After lots of
debugging, head scratching, and experimental changes to the code, the
problem has been narrowed
On Fri, 9 Jul 2010 14:59:09 +0200
Segher Boessenkool wrote:
> >>> Actually, this is something which might need closer attention -
> >>> and maybe some support in the device tree indicating which read or
> >>> write width a device can accept?
> >>
> >> There already is "device-width"; the drivers
On Fri, 9 Jul 2010 00:35:43 -0700
Shawn Jin wrote:
> I changed my toolchain and rebuilt the kernel image. This time all the
> messages below magically displayed on the serial port. :-D Are all
> these the early debugging messages?
Yes, it's an alternate output for the regular console (there are
Hmm, unfortunately, it's usage is not clearly documented in mtd-
physmap.txt,
It's pretty clear I think. Patches for making it better are welcome
of course.
so I never thought of this parameter. And IMHO the problem goes
further - basically *any* chip which is attached to the LPB can be
Actually, this is something which might need closer attention -
and maybe some support in the device tree indicating which read or
write width a device can accept?
There already is "device-width"; the drivers never should use any
other access width unless they *know* that will work.
Wouldn't y
The recent AMCC 405EX Rev D without Security uses a PVR value
that matches the old 405EXr Rev A/B with Security.
The 405EX Rev D without Security would be shown
incorrectly as an 405EXr. The pvr_mask of 0x0004
is no longer sufficient to distinguish the 405EX from 405EXr.
This patch replaces 2
On 09.07.2010, at 11:11, MJ embd wrote:
> On Thu, Jul 1, 2010 at 4:13 PM, Alexander Graf wrote:
>> We just introduced a new PV interface that screams for documentation. So here
>> it is - a shiny new and awesome text file describing the internal works of
>> the PPC KVM paravirtual interface.
>>
On Thu, Jul 1, 2010 at 4:13 PM, Alexander Graf wrote:
> We just introduced a new PV interface that screams for documentation. So here
> it is - a shiny new and awesome text file describing the internal works of
> the PPC KVM paravirtual interface.
>
> Signed-off-by: Alexander Graf
>
> ---
>
> v1
On Fri, Jul 09, 2010 at 04:16:44PM +1000, Benjamin Herrenschmidt wrote:
Hi,
A few questions and some trivial comments below.
> Our handling of debug interrupts on Book3E 64-bit is not quite
> the way it should be just yet. This is a workaround to let gdb
> work at least for now. We ensure that
On 2010-07-09 08:57, divya wrote:
> On Friday 02 July 2010 12:16 PM, divya wrote:
>> On Thursday 01 July 2010 11:55 PM, Maciej Rutecki wrote:
>>> On środa, 30 czerwca 2010 o 13:22:27 divya wrote:
While running fs_racer test from LTP on a POWER6 box against latest
git(2.6.35-rc3-git4 - com
On Fri, Jul 09, 2010 at 09:34:16AM +0200, Jens Axboe wrote:
> On 2010-07-09 08:57, divya wrote:
> > On Friday 02 July 2010 12:16 PM, divya wrote:
> >> On Thursday 01 July 2010 11:55 PM, Maciej Rutecki wrote:
> >>> On środa, 30 czerwca 2010 o 13:22:27 divya wrote:
> While running fs_racer test
I changed my toolchain and rebuilt the kernel image. This time all the
messages below magically displayed on the serial port. :-D Are all
these the early debugging messages?
> Here is the kernel log buf dump. Anything suspicious?
>
> <6>Using My MPC870 machine description
> <5>Linux version 2.6.33
On Friday 02 July 2010 12:16 PM, divya wrote:
On Thursday 01 July 2010 11:55 PM, Maciej Rutecki wrote:
On środa, 30 czerwca 2010 o 13:22:27 divya wrote:
While running fs_racer test from LTP on a POWER6 box against latest
git(2.6.35-rc3-git4 - commitid 984bc9601f64fd) came across the
following
13 matches
Mail list logo
