[Bug 109662] [CI][SHARDS] igt at gem_exec_schedule@* - fail - Failed assertion: result(_read)? == ctx...

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Feb 19 21:25:55 UTC 2019


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

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #3 from Chris Wilson <chris at chris-wilson.co.uk> ---
commit c12b1f87adc4c568b21cc6ed9076b94bea46b010 (HEAD, upstream/master)
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Sun Feb 17 18:14:01 2019 +0000

    i915/gem_exec_schedule: Switch back to gem_set_domain()

    The write hazard lies extend also to the cache-dirty tracking; as we
    purposefully do not tell the kernel we are writing to the bo, it fails
    to note the CPU cache as dirty and so the gem_read() may not
    sufficiently flush the caches prior to reading back from the GPU.

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Antonio Argenziano <antonio.argenziano at intel.com>
    Reviewed-by: Antonio Argenziano <antonio.argenziano at intel.com>

Should be back to where we were... Albeit with the subtle difference between
gem_read and gem_mmap__gtt...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190219/f61d2488/attachment.html>


More information about the intel-gfx-bugs mailing list