summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorZhi A Wang <zhi.wang.linux2@gmail.com>2021-08-26 17:38:34 +0300
committerZhenyu Wang <zhenyuw@linux.intel.com>2021-09-13 16:59:31 +0300
commitd168cd797982db9db617113644c87b8f5f3cf27e (patch)
treeee5c4c490b0c49a887421d2344e362c5e90f67c3 /tools/perf/scripts/python/stackcollapse.py
parent71de496cc489b6bae2f51f89da7f28849bf2836e (diff)
downloadlinux-d168cd797982db9db617113644c87b8f5f3cf27e.tar.xz
drm/i915/gvt: fix the usage of ww lock in gvt scheduler.
As the APIs related to ww lock in i915 was changed recently, the usage of ww lock in GVT-g scheduler needs to be changed accrodingly. We noticed a deadlock when GVT-g scheduler submits the workload to i915. After some investigation, it seems the way of how to use ww lock APIs has been changed. Releasing a ww now requires a explicit i915_gem_ww_ctx_fini(). Fixes: 67f1120381df ("drm/i915/gvt: Introduce per object locking in GVT scheduler.") Cc: Zhenyu Wang <zhenyuw@linux.intel.com> Signed-off-by: Zhi A Wang <zhi.a.wang@intel.com> Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com> Link: http://patchwork.freedesktop.org/patch/msgid/20210826143834.25410-1-zhi.a.wang@intel.com Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions