Re: [PATCH 2/8] drm/i915: Adds graphic address space ballooning logic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Sep 19, 2014 at 06:21:46PM +0000, Tian, Kevin wrote:
> > From: Chris Wilson
> > The implementation also looks backwards. To work correctly with the GTT
> > allocator, you need to preallocate the reserved space such that it can
> > only allocate from the allowed ranges. Similarly, it should evict any
> > conflicting nodes when deballooning.
> 
> Could you elaborate a bit for above suggestion?

My expectation was that the dev_priv->gtt.base.vm would contain exactly
two holes after setup (in the mappable and non-mappable range). To do
that you would explicitly reserve everything barred from this client 
using a set of drm_mm_reserve_node()
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx




[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux