summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2020-11-23 14:37:17 +0300
committerChris Wilson <chris@chris-wilson.co.uk>2020-11-23 20:26:38 +0300
commit46eecfccb4c2b0f258adbafb2e53ca3b822cd663 (patch)
treef05f50cfc8254f11f5aa46b5bafabaf4a8c82afe /tools/perf/scripts/python/stackcollapse.py
parent3aef910d26ef48b8a79d48b006dc04383b86dd31 (diff)
downloadlinux-46eecfccb4c2b0f258adbafb2e53ca3b822cd663.tar.xz
drm/i915/gt: Free stale request on destroying the virtual engine
Since preempt-to-busy, we may unsubmit a request while it is still on the HW and completes asynchronously. That means it may be retired and in the process destroy the virtual engine (as the user has closed their context), but that engine may still be holding onto the unsubmitted compelted request. Therefore we need to potentially cleanup the old request on destroying the virtual engine. We also have to keep the virtual_engine alive until after the sibling's execlists_dequeue() have finished peeking into the virtual engines, for which we serialise with RCU. v2: Be paranoid and flush the tasklet as well. v3: And flush the tasklet before the engines, as the tasklet may re-attach an rb_node after our removal from the siblings. Fixes: 6d06779e8672 ("drm/i915: Load balancing across a virtual engine") Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20201123113717.20500-4-chris@chris-wilson.co.uk
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions