summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorMatthew Auld <matthew.auld@intel.com>2022-03-04 09:59:34 +0000
committerMatthew Auld <matthew.auld@intel.com>2022-03-07 09:24:19 +0000
commit833124a0d1698912f47090683908484a1a937a13 (patch)
treed048259ea46de1669099a0470c5cc08ebb3dcdc9 /tools/perf/scripts/python/stackcollapse.py
parent892bfb8a604d464925edca9a5c3d2b2062c2124d (diff)
drm/i915: limit the async bind to bind_async_flags
If the vm doesn't request async binding, like for example with the dpt, then we should be able to skip the async path and avoid calling i915_vm_lock_objects() altogether. Currently if we have a moving fence set for the BO(even though it might have signalled), we still take the async patch regardless of the bind_async setting, and then later still end up just doing i915_gem_object_wait_moving_fence() anyway. Alternatively we would need to add dummy scratch object which can be locked, just for the dpt. Suggested-by: Thomas Hellström <thomas.hellstrom@linux.intel.com> Signed-off-by: Matthew Auld <matthew.auld@intel.com> Cc: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com> Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20220304095934.925036-2-matthew.auld@intel.com
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions