summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/event_analyzing_sample.py
diff options
context:
space:
mode:
authorMichał Winiarski <michal.winiarski@intel.com>2017-09-18 12:25:35 +0300
committerChris Wilson <chris@chris-wilson.co.uk>2017-09-18 13:18:27 +0300
commita529a1c9db931a5d4fd6683199d73a8363bc7e83 (patch)
treed3e30b4357d7efd5fff9c3c9f20e54c98aa7b874 /tools/perf/scripts/python/event_analyzing_sample.py
parent59db36cf4d67b74f5b8cb001493847464240d136 (diff)
downloadlinux-a529a1c9db931a5d4fd6683199d73a8363bc7e83.tar.xz
drm/i915/guc: Cleanup adding GuC work items
We can just operate on the wq_tail directly (in the process descriptor). This allows us to remove the duplicated tail from the client. While I'm here let's also remove the constants kept in the client and document our locking requirements. This causes a small change in one of GuC debugfs files. We're no longer reporting constant values (which I don't think is a problem), but we're also no longer reporting the tail (does anyone care?). v2: Update tail after wqi contents. (Chris) v3: Really update tail after wqi contents. Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com> Cc: Oscar Mateo <oscar.mateo@intel.com> Signed-off-by: Michał Winiarski <michal.winiarski@intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Link: https://patchwork.freedesktop.org/patch/msgid/20170918092536.12287-1-michal.winiarski@intel.com Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions