<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [KBL APL SKL BSW BDW]igt/gem_ppgtt/flink-and-close-vma-leak fails"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90400#c18">Comment # 18</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [KBL APL SKL BSW BDW]igt/gem_ppgtt/flink-and-close-vma-leak fails"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90400">bug 90400</a>
from <span class="vcard"><a class="email" href="mailto:yann.argotti@intel.com" title="yann <yann.argotti@intel.com>"> <span class="fn">yann</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=90400#c17">comment #17</a>)
<span class="quote">> commit b1f788c6acb2f34622dd5f4c3d5210c6e3945e78
> Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
> Date: Thu Aug 4 07:52:45 2016 +0100
>
> drm/i915: Release vma when the handle is closed
>
> In order to prevent a leak of the vma on shared objects, we need to
> hook into the object_close callback to destroy the vma on the object for
> this file. However, if we destroyed that vma immediately we may cause
> unexpected application stalls as we try to unbind a busy vma - hence we
> defer the unbind to when we retire the vma.
>
> v2: Keep vma allocated until closed. This is useful for a later
> optimisation, but it is required now in order to handle potential
> recursion of i915_vma_unbind() by retiring itself.
> v3: Comments are important.</span >
Christophe, please re-test and close the bug if this issue is not occurring
anymore</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>