On Thu, Aug 15, 2013 at 04:05:56PM +0200, Daniel Vetter wrote:
On Wed, Aug 14, 2013 at 10:15:50AM +0200, Daniel Vetter wrote:
On Wed, Aug 14, 2013 at 10:06:30AM +0200, Daniel Vetter wrote:
On Tue, Aug 13, 2013 at 06:09:06PM -0700, Ben Widawsky wrote:
VMAs can be created and not bound.
On Tue, Aug 13, 2013 at 06:09:06PM -0700, Ben Widawsky wrote:
VMAs can be created and not bound. One may think of it as lazy cleanup,
and safely gloss over the conditions which manufacture it. In either
case, when the object backing the i915 vma is destroyed, we must cleanup
the vma without
On Wed, Aug 14, 2013 at 10:06:30AM +0200, Daniel Vetter wrote:
On Tue, Aug 13, 2013 at 06:09:06PM -0700, Ben Widawsky wrote:
VMAs can be created and not bound. One may think of it as lazy cleanup,
and safely gloss over the conditions which manufacture it. In either
case, when the object
On Tue, Aug 13, 2013 at 06:09:06PM -0700, Ben Widawsky wrote:
VMAs can be created and not bound. One may think of it as lazy cleanup,
and safely gloss over the conditions which manufacture it. In either
case, when the object backing the i915 vma is destroyed, we must cleanup
the vma without
VMAs can be created and not bound. One may think of it as lazy cleanup,
and safely gloss over the conditions which manufacture it. In either
case, when the object backing the i915 vma is destroyed, we must cleanup
the vma without stumbling into a bunch of pitfalls that assume the vma
is bound.
