<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [BAT][GDG] Failed assertion: gtt[1024*i] == ~i in igt@prime_vgem@basic-gtt"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102577#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [BAT][GDG] Failed assertion: gtt[1024*i] == ~i in igt@prime_vgem@basic-gtt"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102577">bug 102577</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>This is just telling us that the GTT/WC on i915g isn't fully coherent, that a
write into the GTT isn't immediately visible by a read in WC. Very similar to
gem_mmap_gtt/coherency (which also fails) but different timing due to using WC
rather than WB.
Not sure what we can do to prevent userspace falling into this trap. Ban PRIME
on i915g? That seems overkill -- the same coherency issue is there on
byt/bsw/bxt/glk, we just haven't hit it on this path.
Move the fine grained coherency check (i.e. concurrent access to vgem and i915
mmaps) to another test and accept the failure.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>