On 8/10/20 12:30 PM, Maarten Lankhorst wrote:
This is the last part outside of selftests that still don't use the
correct lock ordering of timeline->mutex vs resv_lock.

With gem fixed, there are a few places that still get locking wrong:
- gvt/scheduler.c
- i915_perf.c
- Most if not all selftests.

Changes since v1:
- Add intel_engine_pm_get/put() calls to fix use-after-free when using
   intel_engine_get_pool().

Signed-off-by: Maarten Lankhorst <maarten.lankho...@linux.intel.com>

LGTM.

Reviewed-by: Thomas Hellström <thomas.hellst...@intel.com>


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Reply via email to