[Bug 103438] [IGT] drv_selftest subtest mock_evict/live_contexts incompletes

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Oct 25 14:38:32 UTC 2017


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

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

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

--- Comment #5 from Chris Wilson <chris at chris-wilson.co.uk> ---
commit 20ccd4d3f689ac14dce8632d76769be0ac952060
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Tue Oct 24 23:08:55 2017 +0100

    drm/i915: Use same test for eviction and submitting kernel context

    During evict, we wish to idle the GPU if we see that the GGTT is full.
    However, our test for idle in i915_gem_evict_something() and in
    i915_gem_switch_to_kernel_context() do not match leading to
    disappointment - we never believe that we are idle and keep trying to
    flush the GGTT ad infinitum.

    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=103438
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Joonas Lahtinen <joonas.lahtinen at linux.intel.com>
    Cc: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
    Cc: Mika Kuoppala <mika.kuoppala at intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20171024220855.30155-2-chris@chris-wilson.co.uk
    Reviewed-by: Joonas Lahtinen <joonas.lahtinen at linux.intel.com>

Fixes the first issue of mock_evict.

The trace for live_contexts needs kasan and a confirmation that you are
carrying the core-for-CI fixups?

Also since it is a separate bug, please refile it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact 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/20171025/59d19c45/attachment.html>


More information about the intel-gfx-bugs mailing list