On Wed, Jul 03, 2013 at 11:58:31PM +0200, Daniel Vetter wrote: > On Wed, Jul 3, 2013 at 11:44 PM, Ben Widawsky <ben at bwidawsk.net> wrote: > > Yes. It won't be a requirement for mesa to know, but since I want to > > kill aliasing ppgtt as much as possible, I intend to update getparam to > > both set 0 to aliasing, and a new one for ppgtt. > > We use that one essentially to decide whether the hw uses ppgtt or > not, aliasing kinda doesn't matter. So to keep api I guess we need to > keep that one enabled. Although only i-g-t really cares I think, but > keeping it working would still be nice. Maybe just add a comment to > the #define explaining what's going on? > -Daniel It's a bit off topic for this series, but I don't see any reason to keep it working. If it doesn't end up being too much trouble, I can - but in actuality on the kernel would be able to use it. Exposing the param as true to user space would be a lie. I was planning to update the IGT tests to support both things FWIW. > -- > Daniel Vetter > Software Engineer, Intel Corporation > +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- Ben Widawsky, Intel Open Source Technology Center
