From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [PATCH] drm/i915: Do not leak VMAs (and PPGTT VMs) of imported flinked objects
Date: Mon, 20 Apr 2015 14:11:39 +0100 [thread overview]
Message-ID: <5534FB0B.1020006@linux.intel.com> (raw)
In-Reply-To: <20150420125852.GC17348@nuc-i3427.alporthouse.com>
On 04/20/2015 01:58 PM, Chris Wilson wrote:
> On Mon, Apr 20, 2015 at 01:53:03PM +0100, Tvrtko Ursulin wrote:
>>> No we can't do this, as it makes close sync and so can have disasterous
>>> effects on performance (though mitigated chiefly by userspace
>>> agressively caching bo) and also the unbind is very likely to fail,
>>> though admittedly the fbcon copy should be before X starts (ab)using
>>> signals - hence nasty WARN_ON.
>>>
>>> Plus also walking this linear list is quite painful in certain abusive
>>> tests. My preference for fixing this bug would be via vma active
>>> references and auto-unbinding on retirement after a close.
>>
>> Why this is any different today with GEM_CLOSE having pretty similar
>> VMA unbind loop? Is the typical (and interesting) case not that
>> GEM_CLOSE will trigger gem_object_close and gem_object_free at the
>> same invocation?
>
> We have such a cleanup loop in free_object, but we have an active
> reference to ensure that we only do so once the object is idle (and
> unbinding won't cause to wait).
Is that a predominant situation - closing of active objects vs inactive?
It would be surprising (to me).
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-04-20 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 12:14 [PATCH] drm/i915: Do not leak VMAs (and PPGTT VMs) of imported flinked objects Tvrtko Ursulin
2015-04-20 12:36 ` Chris Wilson
2015-04-20 12:53 ` Tvrtko Ursulin
2015-04-20 12:58 ` Chris Wilson
2015-04-20 13:11 ` Tvrtko Ursulin [this message]
2015-04-20 13:33 ` Chris Wilson
2015-04-20 16:57 ` shuang.he
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5534FB0B.1020006@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=tvrtko.ursulin@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.