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

Ankitprasad Sharma ankitprasad.r.sharma at intel.com
Tue Jun 7 08:52:28 UTC 2016


On Wed, 2016-06-01 at 11:31 +0100, Tvrtko Ursulin wrote:
> On 31/05/16 07:19, ankitprasad.r.sharma at intel.com wrote:
> > From: Ankitprasad Sharma <ankitprasad.r.sharma at intel.com>
.
.
.
> > +
> > +void i915_gem_stolen_size_info(struct drm_i915_private *dev_priv,
> > +			       uint64_t *stolen_free,
> > +			       uint64_t *stolen_largest)
> > +{
> > +	struct drm_mm *mm = &dev_priv->mm.stolen;
> > +	struct drm_mm_node *hole;
> > +	uint64_t hole_size, hole_start, hole_end, largest_hole = 0;
> > +	uint64_t total_free = 0;
> > +
> > +	if (dev_priv->mm.volatile_stolen) {
> > +		*stolen_free = 0;
> > +		*stolen_largest = 0;
> > +		return;
> > +	}
> 
> Is it worth having this special case? I am assuming the list below will 
> always be empty in the volatile_stolen case?

FBC uses this space to store the compressed framebuffer, so the list may
not be empty if volatile_stolen case is true.

Thanks,
Ankit




More information about the Intel-gfx mailing list