[Bug 90537] radeonsi bo/va conflict on RADEON_GEM_VA (rscreen->ws->buffer_from_handle returns NULL) - bugzilla-daemon

From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90537] radeonsi bo/va conflict on RADEON_GEM_VA (rscreen->ws->buffer_from_handle returns NULL)
Date: Fri, 22 May 2015 09:30:24 +0000	[thread overview]
Message-ID: <bug-90537-502-vSrBLYcf99@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-90537-502@http.bugs.freedesktop.org/>

[-- Attachment #1.1: Type: text/plain, Size: 878 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=90537

--- Comment #7 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Christian König from comment #6)
> 
> But in your case it looks like that mesa drops the last reference and the
> buffer isn't freed. This means that somebody has still a reference to the
> buffer which is a bit odd.
> 
> It probably points to a bug somewhere.

Not necessarily if the BO is shared. E.g. in the Xorg radeon driver we have to
leak a reference to the fbcon BO because of this issue.

Another possibility is that the same BO is referenced by several GEM handles in
the same DRM fd, e.g. because it's re-imported via GEM flink. In that case, my
patch is probably the wrong solution, as it would make the BO unusable via the
other GEM handle.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1837 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel