diff options
author | 2020-12-17 09:15:24 +0000 | |
---|---|---|
committer | 2020-12-17 19:56:17 +0000 | |
commit | e3ed90b8227eaf7d67ea0a2e81af9a09c71c8e8d (patch) | |
tree | 7d8cebf69e0ad68a816a410e1a9ca786b2dc4f84 /drivers/gpu/drm/i915/gt/intel_gt_pm.c | |
parent | drm/i915: Encode fence specific waitqueue behaviour into the wait.flags (diff) | |
download | linux-dev-e3ed90b8227eaf7d67ea0a2e81af9a09c71c8e8d.tar.xz linux-dev-e3ed90b8227eaf7d67ea0a2e81af9a09c71c8e8d.zip |
drm/i915/gt: Drain the breadcrumbs just once
Matthew Brost pointed out that the while-loop on a shared breadcrumb was
inherently fraught with danger as it competed with the other users of
the breadcrumbs. However, in order to completely drain the re-arming irq
worker, the while-loop is a necessity, despite my optimism that we could
force cancellation with a couple of irq_work invocations.
Given that we can't merely drop the while-loop, use an activity counter on
the breadcrumbs to detect when we are parking the breadcrumbs for the
last time.
Based on a patch by Matthew Brost.
Reported-by: Matthew Brost <matthew.brost@intel.com>
Suggested-by: Matthew Brost <matthew.brost@intel.com>
Fixes: 9d5612ca165a ("drm/i915/gt: Defer enabling the breadcrumb interrupt to after submission")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20201217091524.10258-1-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/i915/gt/intel_gt_pm.c')
0 files changed, 0 insertions, 0 deletions