[Bug 110987] [CI][SHARDS] igt at gem_ctx_engines@independent - fail - Engine instance [2] executed too late

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Aug 13 15:43:25 UTC 2019


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

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

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

--- Comment #5 from Chris Wilson <chris at chris-wilson.co.uk> ---
I claim
commit bfd7241fa594d772e1414574e09d1e4d9fa6643a
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Wed Jun 26 11:26:10 2019 +0100

    i915/gem_ctx_engine: Drip feed requests into 'independent'

    The intent of the test is to exercise that each channel in the engine[]
    is an independent context/ring/timeline. It setups 64 channels pointing
    to rcs0 and then submits one request to each in turn waiting on a
    timeline that will force them to run out of submission order. They can
    only run in fence order and not submission order if the timelines of
    each channel are truly independent.

    However, we released the fences en masse, and once the requests are
    ready they are independent and may be executed in any order by the HW,
    especially true with timeslicing that may reorder the requests on a
    whim. So instead of releasing all requests at once, increment the
    timeline step by step and check we get our results advancing. If the
    requests can not be run in fence order and fall back to submission
    order, we will time out waiting for our incremental results and trigger
    a few GPU hangs.

    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110987
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Reviewed-by: Andi Shyti <andi.shyti at intel.com>

is the fix here.

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


More information about the intel-gfx-bugs mailing list