<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Redraw lag on Ivy Bridge since 1f6dfc9df678"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97914#c38">Comment # 38</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Redraw lag on Ivy Bridge since 1f6dfc9df678"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97914">bug 97914</a>
from <span class="vcard"><a class="email" href="mailto:jdelvare@suse.de" title="Jean Delvare <jdelvare@suse.de>"> <span class="fn">Jean Delvare</span></a>
</span></b>
<pre>Indeed Haswell is affected as well ;-)
I just realized that Mesa includes driver-specific code. My previous comment
naively assumed that Mesa was hardware-agnostic. Obviously, if Mesa includes
intel-specific code, then the bug can indeed be in that part of the stack, and
I understand how the issue could not affect other drivers having undergone
similar optimizations. Sorry for the incorrect claim.
That being said, given that this is only a performance optimization, and its
relevance was estimated before fixing the Mesa side of things, maybe it should
be evaluated again with the Mesa changes applied. As I suppose the changes on
the Mesa side will slow things down a bit again, it may no longer be worth it.
At any rate, if the changes are still deemed worth, the ones in Mesa should
have gone in first. As it stands, the net result for users is a regression.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>