summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2018-09-14 15:35:04 +0300
committerChris Wilson <chris@chris-wilson.co.uk>2018-09-14 16:23:34 +0300
commit666424abfb863e3e51fcd35baad5f242fc69d314 (patch)
tree1dc0a7efa3cdc937937a6094d3745a44b425b6fb /tools/perf/scripts/python/export-to-postgresql.py
parent37d7c9cc2eb6620bf1130de1ca28eb1da0b8ede8 (diff)
downloadlinux-666424abfb863e3e51fcd35baad5f242fc69d314.tar.xz
drm/i915/execlists: Use coherent writes into the context image
That we use a WB mapping for updating the RING_TAIL register inside the context image even on !llc machines has been a source of consternation for every reader. It appears to work on bsw+, but it may just have been that we have been incredibly bad at detecting the errors. v2: With extra enthusiasm. v3: Drop force of map type for pinned default_state as by the time we pin it, the map type is always WB and doesn't conflict with the earlier use by ce->state. v4: Transfer engine->default_state from MAP_WC to MAP_WB on creation so we do not need the MAP_FORCE littered around the backends Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180914123504.2062-3-chris@chris-wilson.co.uk
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions