aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-report
diff options
context:
space:
mode:
authorVille Syrjälä <[email protected]>2016-01-22 18:41:24 +0200
committerVille Syrjälä <[email protected]>2016-08-11 18:34:12 +0300
commit60d5f2a45b5f714ad9a421d2f22c15e7beaef979 (patch)
tree4bd034ab7f7b889dc05b6d951e5b39068c845e5f /tools/perf/scripts/python/bin/stackcollapse-report
parentc2ff7370aee6ba750859d7008d05c68e873d7c7b (diff)
drm/i915: Limit fb x offset due to fences
If there's a fence on the object it will be aligned to the start of the object, and hence CPU rendering to any fb that straddles the fence edge will come out wrong due to lines wrapping at the wrong place. We have no API to manage fences on a sub-object level, so we can't really fix this in any way. Additonally gen2/3 fences are rather coarse grained so adjusting the offset migth not even be possible. Avoid these problems by requiring the fb layout to agree with the fence layout (if present). v2: Rebase due to i915_gem_object_get_tiling() & co. Signed-off-by: Ville Syrjälä <[email protected]> Reviewed-by: Sivakumar Thulasimani <[email protected]> Link: http://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions