<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [All regression] Render error when running Unigine-Heave_v4.0" href="https://bugs.freedesktop.org/show_bug.cgi?id=91916#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [All regression] Render error when running Unigine-Heave_v4.0" href="https://bugs.freedesktop.org/show_bug.cgi?id=91916">bug 91916</a> from <a class="email" href="mailto:yex.tian@intel.com" title="ye.tian <yex.tian@intel.com>"> ye.tian</a> <pre>By bisect, shows the first bad mesa commit is 5ead4487. commit 5e3974338ed7ea49a41405f8c2e4bcd5fd1f5c80 Author: Marek Olšák <<a href="mailto:marek.olsak@amd.com">marek.olsak@amd.com</a>> AuthorDate: Thu Jul 16 14:54:50 2015 +0200 Commit: Marek Olšák <<a href="mailto:marek.olsak@amd.com">marek.olsak@amd.com</a>> CommitDate: Thu Jul 23 00:59:24 2015 +0200 gallium/radeon: remove buffer_unmap calls that can potentially decrease perf buffer_unmap is currently a no-op on radeon and done correctly on amdgpu. I plan to fix it for radeon, but before that, all occurences of buffer_unmap that can negatively affect performance in the future must be removed. There are 2 reasons for removing buffer_unmap calls: - There is a likelihood that buffer_map will be called again, so we don't want to unmap yet. - The buffer is being released, which automatically unmaps it. Reviewed-by: Michel Dänzer <<a href="mailto:michel.daenzer@amd.com">michel.daenzer@amd.com</a>></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>