Hi all,
Those of us working on the POWER toolchain can envision a certain class
of customers who may benefit from intelligently disabling certain
register class enable bits on context switches, i.e. not disabling by
default.
Currently, per process, if the MSR enable bits for FPs, VRs or
Another option might be simply to say that if an app has used FP,
VMX or
VSX -once-, then it's likely to do it again and just keep re-enabling
it :-)
I'm serious here, do we know that many cases where these things are
used
seldomly once in a while ?
For FP, I believe many apps use it only
It's very likely that a process which results in the
enabling of FP,VMX, or VSX may continue to use the facility for the
duration of it's lifetime. Threads would be even more likely to
exhibit
this behavior.
The case where this might not be true is if we use VMX or VSX for
string
routine
On Sat, 2009-03-14 at 14:49 +0100, Segher Boessenkool wrote:
Another option might be simply to say that if an app has used FP,
VMX or
VSX -once-, then it's likely to do it again and just keep re-enabling
it :-)
I'm serious here, do we know that many cases where these things are
Original-Nachricht
Datum: Thu, 12 Mar 2009 11:32:19 +0100
Von: Roderick Colenbrander thunderbir...@gmx.net
An: linuxppc-dev@ozlabs.org
Betreff: DTS file PCI / i8259 for Xilinx ML510
...
The freescale boards define the pci bus like below and connect ULI M1575
peripherals
On Sat, Mar 14, 2009 at 9:03 AM, Johns Daniel jdan...@computer.org wrote:
TSEC/MDIO will not work with older device trees because of a semicolon at
the end of a macro resulting in an empty for loop body.
This fix only applies to 2.6.28; this code is gone in 2.6.29, according to
Grant Likely!
