diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2012-04-17 15:31:31 +0100 |
|---|---|---|
| committer | Daniel Vetter <daniel.vetter@ffwll.ch> | 2012-04-18 13:34:30 +0200 |
| commit | 61050808bb019ebea966b7b5bfd357aaf219fb51 (patch) | |
| tree | 72cc9ecdf833fc3bee5e66355acf985f1e3e964e /tools/perf/scripts/python/syscall-counts.py | |
| parent | 9ce079e4812c41c5f4ee9ea116c768b8939197d6 (diff) | |
drm/i915: Refactor put_fence() to use the common fence writing routine
One clarification that we make is to the existing semantics of
obj->tiling_changed to only mean that we need to update an associated
fence register (including the NO_FENCE when executing an untiled but
fenced GPU command). If we do not have a fence register or pending
fenced GPU access for the object (after put_fence() for example), then
we can clear the tiling_changed flag as any fence will necessarily be
rewritten upon acquisition.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions