<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:u9vata@gmail.com" title="Richard Thier <u9vata@gmail.com>"> <span class="fn">Richard Thier</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Radeon: heavy r300 performance drop regression between 11.x and 19.x"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110781">bug 110781</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Attachment #144427 is obsolete</td>
<td>
</td>
<td>1
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Radeon: heavy r300 performance drop regression between 11.x and 19.x"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110781#c26">Comment # 26</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Radeon: heavy r300 performance drop regression between 11.x and 19.x"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110781">bug 110781</a>
from <span class="vcard"><a class="email" href="mailto:u9vata@gmail.com" title="Richard Thier <u9vata@gmail.com>"> <span class="fn">Richard Thier</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=144439" name="attach_144439" title="Hacky fix working also for 19.x versions">attachment 144439</a> <a href="attachment.cgi?id=144439&action=edit" title="Hacky fix working also for 19.x versions">[details]</a></span> <a href='page.cgi?id=splinter.html&bug=110781&attachment=144439'>[review]</a>
Hacky fix working also for 19.x versions
I can confirm the problem with the "possible fix" is because
radeon_get_heap_index does not handle both GTT and VRAM domains at the same
time, but r300 still asks for that.
Added a hacky fix that works on 19.x versions but forces VRAM domain. This
highlights problematic areas for the new versions. I think this latter issue is
because of bitrot happening with r300 as now we re-enabled a code path that was
never happening after the slowdown in 17.x as analysed before.
PS.: Of course the "possible fix" still works when applied directly to the 17.x
commit that made things slow and that is the better direction, just not to the
latest code because of this issue.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>