diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2018-07-30 08:53:51 +0100 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2018-07-30 10:33:21 +0100 |
| commit | f6844a85e0c96a55c61fa3e611f414999b11e4de (patch) | |
| tree | f574a8f0ba4d40499a946ecd27599b6a26cea552 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 39f3be162c46bc2349ad7a5bd89536eb83561c81 (diff) | |
drm/i915/selftests: Replace opencoded clflush with drm_clflush_virt_range
We occasionally see that the clflush prior to a read of GPU data is
returning stale data, reminiscent of much earlier bugs fixed by adding a
second clflush for serialisation. As drm_clflush_virt_range() already
supplies the workaround, use it rather than open code the clflush
instruction.
References: 396f5d62d1a5 ("drm: Restore double clflush on the last partial cacheline")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180730075351.15569-3-chris@chris-wilson.co.uk
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions