I'd like to replace my old pmac G4. Are there affordable ppc systems on the
market today ? Perhaps some dev board with a p4080 or newer ?
--
Giuliano.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linux
Hello Carl,
On 03/01/2012 06:45 PM, Carl E. Love wrote:
Victor:
The performance counter tools perf and OProfile capture the value of the
instruction pointer at the time an interrupt occurs. The file
arch/powerpc/oprofile/op_model_power4.c contains the OProfile interrupt
handler used for Power 4
Hi Bjorn,
On Fri, 2 Mar 2012 10:10:02 -0700 Bjorn Helgaas wrote:
>
> Thanks a lot for the test report and the bisection. I wish I had a
> machine to test on so I wouldn't have to bother you about it.
That's OK.
> Any chance you could point me at the complete before/after dmesg logs?
> There s
On Fri, 2012-03-02 at 10:10 -0700, Bjorn Helgaas wrote:
> On Thu, Mar 1, 2012 at 11:06 PM, Stephen Rothwell
> wrote:
> > Hi Jesse,
> >
> > Staring with next-20120227, one of my boot tests is failing like this:
>
> Hi Stephen,
>
> Thanks a lot for the test report and the bisection. I wish I had
On 02/28/2012 09:54 PM, Liu Qiang-B32616 wrote:
Hi Jeff,
Do you plan to apply it to upstream, or any suggestions? Thanks.
This patch has been in libata-dev (and thus linux-next) for about 2 weeks...
___
Linuxppc-dev mailing list
Linuxppc-dev@lists
On 03/02/2012 10:30 AM, Alexander Graf wrote:
>
> On 02.03.2012, at 17:20, Scott Wood wrote:
>
>> On Fri, Mar 02, 2012 at 03:12:33PM +0100, Alexander Graf wrote:
>>> When running inside a virtual machine, we can not modify timebase, so
>>> let's just not call the functions for it then.
>>>
>>> Th
On Thu, Mar 1, 2012 at 11:06 PM, Stephen Rothwell wrote:
> Hi Jesse,
>
> Staring with next-20120227, one of my boot tests is failing like this:
Hi Stephen,
Thanks a lot for the test report and the bisection. I wish I had a
machine to test on so I wouldn't have to bother you about it.
Any chanc
On 02.03.2012, at 17:20, Scott Wood wrote:
> On Fri, Mar 02, 2012 at 03:12:33PM +0100, Alexander Graf wrote:
>> When running inside a virtual machine, we can not modify timebase, so
>> let's just not call the functions for it then.
>>
>> This resolves hangs when booting e500 SMP guests on overco
On Fri, Mar 02, 2012 at 03:12:33PM +0100, Alexander Graf wrote:
> When running inside a virtual machine, we can not modify timebase, so
> let's just not call the functions for it then.
>
> This resolves hangs when booting e500 SMP guests on overcommitted hosts.
>
> Reported-by: Stuart Yoder
> Si
On Mar 2, 2012, at 1:08 AM, Liu Gang wrote:
> For the file "arch/powerpc/sysdev/fsl_rmu.c", there will be some compile
> errors while using the corenet64_smp_defconfig:
>
> .../fsl_rmu.c:315: error: cast from pointer to integer of different size
> .../fsl_rmu.c:320: error: cast to pointer from i
On 12-03-02 02:08 AM, Liu Gang wrote:
> For the file "arch/powerpc/sysdev/fsl_rmu.c", there will be some compile
> errors while using the corenet64_smp_defconfig:
>
> .../fsl_rmu.c:315: error: cast from pointer to integer of different size
> .../fsl_rmu.c:320: error: cast to pointer from integer o
When running inside a virtual machine, we can not modify timebase, so
let's just not call the functions for it then.
This resolves hangs when booting e500 SMP guests on overcommitted hosts.
Reported-by: Stuart Yoder
Signed-off-by: Alexander Graf
---
arch/powerpc/platforms/85xx/smp.c |7 +++
> For the file "arch/powerpc/sysdev/fsl_rmu.c", there will be
> some compile errors while using the corenet64_smp_defconfig:
I'm sure that replacing 'u32' with 'unsigned long'
is really the best thing to do here.
It looks to me as though they should be some pointer type.
David
__
The perfmon interrupt is the sole user of a special variant of the
interrupt prolog which differs from the one used by external and timer
interrupts in that it saves the non-volatile GPRs and doesn't turn the
runlatch on.
The former is unnecessary and the later is arguably incorrect, so
let's clea
Some exceptions would unconditionally disable interrupts on entry,
which is fine, but calling lockdep every time not only adds more
overhead than strictly needed, but also means we get quite a few
"redudant" disable logged, which makes it hard to spot the really
bad ones.
So instead, split the mac
This series goes through various bits and pieces of our exception
and interrupts handling, fixin bugs, cleaning up code, adding
missing functionality, etc... The last patch of the series is
a reworked variant of my lazy irq rework.
This needs a good review as it touches pretty nasty bits of code
a
We unconditionally hard enable interrupts. This is unnecessary as
syscalls are expected to always be called with interrupts enabled.
While at it, we add a WARN_ON if that is not the case and
CONFIG_TRACE_IRQFLAGS is enabled (we don't want to add overhead
to the fast path when this is not set thoug
If we get a floating point, altivec or vsx unavaible interrupt in
kernel, we trigger a kernel error. There is no point preserving
the interrupt state, in fact, that can even make debugging harder
as the processor state might change (we may even preempt) between
taking the exception and landing in a
Other architectures such as x86 and ARM have been growing
new support for features like retrying page faults after
dropping the mm semaphore to break contention, or being
able to return from a stuck page fault when a SIGKILL is
pending.
This refactors our implementation of do_page_fault() to
move
On 64-bit, the mfmsr instruction can be quite slow, slower
than loading a field from the cache-hot PACA, which happens
to already contain the value we want in most cases.
Signed-off-by: Benjamin Herrenschmidt
---
arch/powerpc/include/asm/exception-64s.h |2 +-
arch/powerpc/include/asm/hw_irq
This removes the various bits of assembly in the kernel entry,
exception handling and SLB management code that were specific
to running under the legacy iSeries hypervisor which is no
longer supported.
Signed-off-by: Benjamin Herrenschmidt
---
arch/powerpc/include/asm/exception-64s.h | 15
Also use local_paca instead of get_paca() to avoid getting into
the smp_processor_id() debugging code from the debugger
Signed-off-by: Benjamin Herrenschmidt
---
arch/powerpc/xmon/xmon.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/xmon/xmon.c b/arc
We currently turn interrupts back to their previous state before
calling do_page_fault(). This can be annoying when debugging as
a bad fault will potentially have lost some processor state before
getting into the debugger.
We also end up calling some generic code with interrupts enabled
such as no
The current implementation of lazy interrupts handling has some
issues that this tries to address.
We don't do the various workarounds we need to do when re-enabling
interrupts in some cases such as when returning from an interrupt
and thus we may still lose or get delayed decrementer or doorbell
This moves the inlines into system.h and changes the runlatch
code to use the thread local flags (non-atomic) rather than
the TIF flags (atomic) to keep track of the latch state.
The code to turn it back on in an asynchronous interrupt is
now simplified and partially inlined.
Signed-off-by: Benja
When running under a hypervisor that supports stolen time accounting,
we may call C code from the macro EXCEPTION_PROLOG_COMMON in the
exception entry path, which clobbers CR0.
However, the FPU and vector traps rely on CR0 indicating whether we
are coming from userspace or kernel to decide what to
26 matches
Mail list logo
