[Intel-gfx] [PATCH] manage pixmaps with EXA

Jesse Barnes jbarnes at virtuousgeek.org
Thu Apr 9 19:45:14 CEST 2009

On Thu, 09 Apr 2009 10:04:37 -0700
Eric Anholt <eric at anholt.net> wrote:

> On Wed, 2009-04-08 at 16:56 -0700, Jesse Barnes wrote:
> > I started looking at #20739 and it appears to be a server bug in the
> > EXA migration code somewhere.  Rather than digging through that when
> > we're likely to remove EXA support soon, I just added support for
> > driver managed pixmaps, which fixes also fixes the bug.
> > 
> > This is a fairly significant change so close to release, but I
> > thought I'd post it for comments.
> > 
> > The patch isn't actually as big as it appears; it mainly moves the
> > UXA pixmap create/destroy routines up above the EXA init call so
> > they can be used for both cases.
> NAK -
> If you have kernel memory management, you should be using UXA.
> Non-kernel memory management is the only reason we have EXA around at
> all, since we get stuck with non-kernel memory management on the
> second server pre-KMS.  This patch would remove that support, so we
> might as well just remove EXA entirely in that case.

As we discussed the alternative would be to beef up the fake bufmgr to
handle that case better.  Aside from providing GTT maps in the fake
bufmgr what else do you think needs to be done?

Jesse Barnes, Intel Open Source Technology Center

More information about the Intel-gfx mailing list