<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - [sna ivb] corruption with chromium"
href="https://bugs.freedesktop.org/show_bug.cgi?id=66990#c25">Comment # 25</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - [sna ivb] corruption with chromium"
href="https://bugs.freedesktop.org/show_bug.cgi?id=66990">bug 66990</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>If you are keen, you can try:
the userptr branch from <a href="http://cgit.freedesktop.org/~ickle/linux-2.6">http://cgit.freedesktop.org/~ickle/linux-2.6</a>
and compiling the ddx with ./configure --enable-userptr <usual configure
options>
The difference will be subtle, only a path where we need to operate on a busy
target will use the userptr directly. At the moment, we will allocate a staging
buffer to perform the copy. My feeling is that we are missing some barrier
around that staging buffer and the GPU reads garbage instead of the updated
content from chromium. So if switching to userptr does fix the corruption, I
think that points towards the staging buffer.</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>