[Bug 79238] [SNA G33/31] xorg/ddx hits kgem_check_many_bo_fenced: Assertion `bo->refcnt' failed.
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon May 26 12:50:12 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=79238
Chris Wilson <chris at chris-wilson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #6 from Chris Wilson <chris at chris-wilson.co.uk> ---
Went ahead and pushed:
commit 9f4f855ba37966fb91d31e9081d03cf72affb154
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date: Mon May 26 07:06:18 2014 +0100
sna: Implicit release of upload buffers considered bad
Currently upload buffers are automatically decoupled when the buffer is
retired. As retiring can happen during command setup after we have
selected which bo to render with, this can free the bo we plan to use.
Which is bad.
Instead of making the release of upload buffers automatic, we manually
check whether the buffer is idle before use as a source to consider
scrapping it and replacing it with a real GPU bo. This is likely to keep
upload buffers alive for longer (limiting reuse between Pixmaps but
making reuse of the buffer within a Pixmap more likely) which is both
good and bad. (Good - may improve the content cache, bad - may increase
the amount of memory used by upload buffers for arbitrary long periods.)
Reported-by: Matti Hämäläinen <ccr at tnsp.org>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=79238
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
commit b508d8f3318c42a2a87b7731789b1d03610e9b46
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date: Mon May 26 06:54:03 2014 +0100
sna: Assert that we do not replace active IO buffers
References: https://bugs.freedesktop.org/show_bug.cgi?id=79238
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140526/d04d14bc/attachment.html>
More information about the intel-gfx-bugs
mailing list