summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorJohn Harrison <John.C.Harrison@Intel.com>2015-02-13 14:48:10 +0300
committerDaniel Vetter <daniel.vetter@ffwll.ch>2015-02-26 00:43:29 +0300
commit8e004efc16541e7f6e35673449195db5d1f92f40 (patch)
tree7b0d48fb698ef222a3d7c8a4d1493ef4234380a0 /tools/perf/scripts/python
parent06dc68d68090ce6da12f7fde03e64a32f0f6e5d0 (diff)
downloadlinux-8e004efc16541e7f6e35673449195db5d1f92f40.tar.xz
drm/i915: Rename 'flags' to 'dispatch_flags' for better code reading
There is a flags word that is passed through the execbuffer code path all the way from initial decoding of the user parameters down to the very final dispatch buffer call. It is simply called 'flags'. Unfortuantely, there are many other flags words floating around in the same blocks of code. Even more once the GPU scheduler arrives. This patch makes it more obvious exactly which flags word is which by renaming 'flags' to 'dispatch_flags'. Note that the bit definitions for this flags word already have an 'I915_DISPATCH_' prefix on them and so are not quite so ambiguous. OTC-Jira: VIZ-1587 Signed-off-by: John Harrison <John.C.Harrison@Intel.com> [danvet: Resolve conflict with Chris' rework of the bb parsing.] Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions