More 16 vs 24 bpp profiling
Marco Pesenti Gritti
mpgritti at gmail.com
Wed Sep 12 11:21:57 EDT 2007
On 9/12/07, Dan Williams <dcbw at redhat.com> wrote:
> On Tue, 2007-09-11 at 14:19 -0400, Bernardo Innocenti wrote:
> > On 09/11/2007 01:32 PM, Bernardo Innocenti wrote:
> > > The 16bpp codepath has to be broken somewhere if
> > > it takes twice the time to copy half the bits :-)
> > It strikes me that we don't see any time spent in
> > pixman_fill_mmx(), even though it's not inlinable.
> > For some reason, pixman thinks it cannot accelerate
> > 16bpp fills with MMX, at least on the Geode.
> > Might be worth investigating...
> We did have to patch the MMX check in pixman long ago, maybe that got
> broken somehow? There were actually two, an update to the cpu flags and
> also a strcmp() on the processor ID that had to be fixed to get pixman
> to detect MMX capability on the geode.
Yeah this the current check:
(strcmp(vendor, "AuthenticAMD") == 0 ||
strcmp(vendor, "Geode by NSC") == 0))
I think Jordan mentioned that the LX is not using "Geode by NSC" anymore.
More information about the Devel