[Bug 111626] [CI][SHARDS] igt at perf_pmu@busy-idle-no-semaphores-bcs0 - dmesg-warn - WARNING: possible irq lock inversion dependency detected

[bugzilla-daemon at freedesktop.org]

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

--- Comment #28 from Chris Wilson <chris at chris-wilson.co.uk> ---
commit c9ad602feabe4271d2adf1bdae5d8b20c2dc84f1
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Thu Nov 14 17:25:35 2019 +0000

    drm/i915: Split i915_active.mutex into an irq-safe spinlock for the rbtree

    As we want to be able to run inside atomic context for retiring the
    i915_active, and we are no longer allowed to abuse mutex_trylock, split
    the tree management portion of i915_active.mutex into an irq-safe
    spinlock.

    References: a0855d24fc22d ("locking/mutex: Complain upon mutex API misuse
in IRQ contexts")
    References: https://bugs.freedesktop.org/show_bug.cgi?id=111626
    Fixes: 274cbf20fd10 ("drm/i915: Push the i915_active.retire into a worker")
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Tvrtko Ursulin <tvrtko.ursulin at linux.intel.com>
    Cc: Matthew Auld <matthew.auld at intel.com>
    Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin at linux.intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20191114172535.1116-1-chris@chris-wilson.co.uk

will get rid of most of the culprits, but we still have the
intel_engine_pm_put() from inside i915_pmu.c to worry about. I might just stop
pushing for that to be immediate and always schedule the work.

-- 
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/20191114/3a2ef3f5/attachment-0001.html>