<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [regression bisected] Stuttering in games caused by commit 4dfd6486 "drm: Use vblank timestamps to guesstimate how many vblanks were missed""
href="https://bugs.freedesktop.org/show_bug.cgi?id=93147#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [regression bisected] Stuttering in games caused by commit 4dfd6486 "drm: Use vblank timestamps to guesstimate how many vblanks were missed""
href="https://bugs.freedesktop.org/show_bug.cgi?id=93147">bug 93147</a>
from <span class="vcard"><a class="email" href="mailto:mario.kleiner@tuebingen.mpg.de" title="Mario Kleiner <mario.kleiner@tuebingen.mpg.de>"> <span class="fn">Mario Kleiner</span></a>
</span></b>
<pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=93147#c7">comment #7</a>)
<span class="quote">> Mario, can you submit your fix(es) for inclusion?</span >
Still on it. The proper patch for radeon-kms will hopefully be finished and
tested within a day or so. But ideally i'd need some feedback on the line
buffer sizes/partitions/watermarks - see my last e-mail on that. Otherwise i'll
have to use very conservative guesstimates for the fudge constant in the
current patch to be on the safe side.
amdgpu-kms will have the same problem and solution, but i haven't looked into
how to hook that up, with the difference in how the display engine code is
hooked up.
thanks,
-mario</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>