[Bug 108887] [CI][SHARDS] igt at gem_userptr_blits@readonly-unsync - timeout

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Jan 24 16:12:56 UTC 2019


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

Lakshmi <lakshminarayana.vudum at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      i915 platform|                            |CFL, BDW

--- Comment #9 from Lakshmi <lakshminarayana.vudum at intel.com> ---
(In reply to Chris Wilson from comment #7)
> commit 8477ed9aeeaa8afb491d73a4c53d1b7dc64413c6 (upstream/master,
> origin/master, origin/HEAD)
> Author: Chris Wilson <chris at chris-wilson.co.uk>
> Date:   Tue Jan 15 20:50:24 2019 +0000
> 
>     i915/gem_userptr_blits: Only mlock the memfd once, not the arena
>     
>     We multiply the memfd 64k to create a 2G arena which we then attempt to
>     write into after marking read-only. However, when it comes to unlock the
>     arena after the test, performance tanks as the kernel tries to resolve
>     the 64k repeated mappings onto the same set of pages. (Must not be a
>     very common operation!) We can get away with just mlocking the backing
>     store to prevent its eviction, which should prevent the arena mapping
>     from being freed as well.
>     
>     References: https://bugs.freedesktop.org/show_bug.cgi?id=108887
>     Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
>     Reviewed-by: Mika Kuoppala <mika.kuoppala at linux.intel.com>

Last seen this issue drmtip_196 (5 days, 22 hours / 341 runs ago) on SKL.
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_196/fi-skl-6700k2/igt@gem_userptr_blits@readonly-unsync.html

Are these changes are in drmtip already?

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


More information about the intel-gfx-bugs mailing list