[PATCH] add EXA relocation function

[Dave Airlie]

> > >
> > > One possible enhancement would be to call back into a driver provided function
> > > to update the private allocations, but it wouldn't really save any code...
> > >
> > > Any thoughts on this?
> >
> > I'm not sure it's really worth it, compared to using the existing
> > CreatePixmap hook for allocating pixmaps from a generic memory manager
> > such as TTM in the first place. Is there anything the latter can't do
> > that the former can?
>
> I'm curious too, I thought we were going to use one BO per pixmap.
> Redirected direct rendering and texturing from pixmap both requires a
> BO per pixmap to work.
>

Except maybe for glyphs, which really would need a single pixmap
cache, with some pipelined upload for new glyphs..

Dave.