diff options
| author | Imre Deak <[email protected]> | 2013-02-13 21:56:05 +0200 |
|---|---|---|
| committer | Daniel Vetter <[email protected]> | 2013-02-20 00:21:43 +0100 |
| commit | 769ce4643b775496166d09c227b070cc38f9e205 (patch) | |
| tree | 4169bb20e669a36af5c51f80168551aa8da7d669 /tools/perf/scripts/python/syscall-counts.py | |
| parent | 10d8373064762b21e16e73bc7dfde49d68f4e31f (diff) | |
drm/i915: don't clflush gem objects in stolen memory
As explained by Chris Wilson gem objects in stolen memory are always
coherent with the GPU so we don't need to ever flush the CPU caches for
these.
This fixes a breakage - at least with the compact sg patches applied -
during the resume/restore gtt mappings path, when we tried to clflush an
FB object in stolen memory, but since stolen objects don't have backing
pages we passed an invalid page pointer to drm_clflush_page().
Signed-off-by: Imre Deak <[email protected]>
Reviewed-by: Chris Wilson <[email protected]>
Signed-off-by: Daniel Vetter <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions