[Bug 99209] [EGL, i965] dEQP-EGL.functional.sharing.gles2.multithread.simple_egl_server_sync.textures.copyteximage2d_texsubimage2d_render

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jan 9 16:58:25 UTC 2017


https://bugs.freedesktop.org/show_bug.cgi?id=99209

--- Comment #9 from Chad Versace <chadversary at chromium.org> ---
(In reply to Jason Ekstrand from comment #7)
[...]
> 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.

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?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20170109/5fe95f95/attachment-0001.html>


More information about the intel-3d-bugs mailing list