On Tue, Jan 04, 2011 at 09:10:04PM +0100, Daniel Vetter wrote: > On Fri, Dec 31, 2010 at 09:31:23AM +0000, Chris Wilson wrote: > > I'm still leaning towards explicit associate/disassociate ioctls as I > > think that will lead to a simpler userspace API (or at least integrate > > conveniently with the existing libdrm). > > I don't like a separate ioctl to associate/disassociate a buffer from a > context: Conceptually there's no way to change that association without an > execbuf call. Doing the book-keeping as a separate, non-atomic ioctl calls > calls for trouble imho. >
I think there is a distinct possibility that we'll need a way to associate buffers with either the GGTT or the ppGTT. I'm currently trying to figure out if this is actually the case but I haven't yet been able to find exactly which memory objects, if any, must be accessed through the GGTT. Just curious Daniel, if this is the case, does it change your feeling on the IOCTL, or do you still prefer execbuf? Ben _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
