Re: [Intel-gfx] [PATCH 04/11] drm/i915: Extend GET_APERTURE ioctl to report available map space

2015-04-30 Thread Joonas Lahtinen
On ke, 2015-04-29 at 11:27 +0100, Chris Wilson wrote: On Wed, Jan 28, 2015 at 10:59:28AM +0100, Daniel Vetter wrote: Do we have the libdrm patch for this too? Imo there's not much use in this if mesa remains broken, especially since this is for gen2/3 ... most DE use gl nowadays. On the

Re: [Intel-gfx] [PATCH 04/11] drm/i915: Extend GET_APERTURE ioctl to report available map space

2015-04-29 Thread Chris Wilson
On Wed, Jan 28, 2015 at 10:59:28AM +0100, Daniel Vetter wrote: Do we have the libdrm patch for this too? Imo there's not much use in this if mesa remains broken, especially since this is for gen2/3 ... most DE use gl nowadays. On the other hand, there is a bug report open for mesa being broken

Re: [Intel-gfx] [PATCH 04/11] drm/i915: Extend GET_APERTURE ioctl to report available map space

2015-04-29 Thread Chris Wilson
On Wed, Jan 28, 2015 at 10:59:28AM +0100, Daniel Vetter wrote: On Mon, Jan 26, 2015 at 04:43:18AM -0800, Rodrigo Vivi wrote: When constructing a batchbuffer, it is sometimes crucial to know the largest hole into which we can fit a fenceable buffer (for example when handling very large

[Intel-gfx] [PATCH 04/11] drm/i915: Extend GET_APERTURE ioctl to report available map space

2015-01-26 Thread Rodrigo Vivi
When constructing a batchbuffer, it is sometimes crucial to know the largest hole into which we can fit a fenceable buffer (for example when handling very large objects on gen2 and gen3). This depends on the fragmentation of pinned buffers inside the aperture, a question only the kernel can easily