summaryrefslogtreecommitdiff
path: root/tests/prime_mmap_coherency.c
diff options
context:
space:
mode:
authorTiago Vignatti <tiago.vignatti@intel.com>2015-08-10 13:28:37 -0300
committerDaniel Vetter <daniel.vetter@ffwll.ch>2016-02-11 18:16:20 +0100
commit7c89c9d7346ca940a4c5d2828ac0c85921fa52c3 (patch)
tree7be3eb53fad7bd1af759fd4c5499129b659875f4 /tests/prime_mmap_coherency.c
parent35debab2d9690aa6c26528358e882168e90dcb2b (diff)
tests: Add kms_mmap_write_crc for cache coherency tests
This program can be used to detect when CPU writes in the dma-buf mapped object don't land in scanout due cache incoherency. Although this seems a problem inherently of non-LCC machines ("Atom"), this particular test catches a cache dirt on scanout on LLC machines as well. It's inspired in Ville's kms_pwrite_crc.c and can be used also to test the correctness of the driver's begin_cpu_access and end_cpu_access (which requires i915 implementation. To see the need for flush, one has to run using '-n' option to not call the sync ioctls which, via a rather simple CPU hog the system will trashes the caches, while the test will catch the coherency issue. If you now suppress '-n', then things should just work like expected. I tested this with !llc and llc platforms, BTY and IVY respectively. v2: use prime_handle_to_fd_for_mmap instead. v3: merge end_cpu_access() patch with this and provide options to disable sync. v4: use library's prime_sync_{start,end} instead. v7: use CPU hog instead and use testing rounds to catch the sync problems. Signed-off-by: Tiago Vignatti <tiago.vignatti@intel.com> Reviewed-by: Stéphane Marchesin <marcheu@chromium.org> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Diffstat (limited to 'tests/prime_mmap_coherency.c')
0 files changed, 0 insertions, 0 deletions