<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [EGL, i965] dEQP-EGL.functional.sharing.gles2.multithread.simple_egl_server_sync.textures.copyteximage2d_texsubimage2d_render"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99209#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [EGL, i965] dEQP-EGL.functional.sharing.gles2.multithread.simple_egl_server_sync.textures.copyteximage2d_texsubimage2d_render"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99209">bug 99209</a>
from <span class="vcard"><a class="email" href="mailto:chadversary@chromium.org" title="Chad Versace <chadversary@chromium.org>"> <span class="fn">Chad Versace</span></a>
</span></b>
<pre>(In reply to Jason Ekstrand from <a href="show_bug.cgi?id=99209#c7">comment #7</a>)
[...]
<span class="quote">> The solution here is that each context needs to track its own set of
> offsets. There's no real utility in sharing them since each hardware
> context has it's own GTT on modern hardware. On older hardware, we'll do
> the relocation for the first batch we submit with the BO but then the kernel
> will tell us the offset and future batches won't relocate. In either case,
> tracking it globally in libdrm isn't gaining us anything and is, in fact,
> the problem.</span >
I infer that a correct fix (not a hack) would require i965 to stop using, at a
minimum, the libdrm exec functions (drm_intel_*_exec()). We could, to mitigate
the pain of fixing this, and to write a backportable patch, continue using
drm_intel_bo throughout i965; we just need to, at least initially, stop using
drm_intel_*_exec. Do you agree? Am I misunderstanding the problem?</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>