commit | be9dd7fb9fccb7da40e484b10de54b1870c6a5c4 | [log] [tgz] |
---|---|---|
author | Anthony Pesch <apesch@nvidia.com> | Tue Mar 26 12:24:17 2019 -0400 |
committer | Alexander Galazin <Alexander.Galazin@arm.com> | Thu Apr 04 14:20:48 2019 -0400 |
tree | ac6526d34753d8cf972a89225a341dcd0895428f | |
parent | 38db037997d48eca9ed86bdd134430ab03ff5ef6 [diff] |
Fix buffer RAW hazards in MultiQueue synchronization tests The MultiQueue tests emit barriers between command buffers for two reasons: 1. To express the data dependencies between different pipeline stages. 2. To transfer ownership of the resource between queue families. The exclusive sharing mode tests need both of these barriers, while the concurrent mode tests only need to describe the data dependency. Previously, a barrier was only emitted for the exclusive tests, causing the concurrent tests to not have a barrier expressing the data dependencies between the pipeline stages. Now the data dependencies are described for both the exlusive and concurrent tests, while the ownership transfer is only performed for exclusive tests. Affects: dEQP-VK.synchronization.op.multi_queue.*.write_*_read_*.buffer_* Components: Vulkan VK-GL-CTS issue: 1650 Change-Id: Ic3bc83a7dcab8686754aea5267afeb10090038d0 (cherry picked from commit 93dc8a343c7ea67a2c8ffb694b45ff44703fbe6f)
This repository contains a GPU testing suite called dEQP (drawElements Quality Program). dEQP contains tests for several graphics APIs, including OpenGL ES, EGL, and Vulkan.
Up-to-date documentation for the dEQP is available at Android Open Source Project site.
The .qpa logs generated by the conformance tests may contain embedded png images of the results. These can be viewed with the Cherry tool.
This repository includes Khronos Vulkan CTS under external/vulkancts
directory. For more information see Vulkan CTS README.
This repository includes Khronos OpenGL / OpenGL ES CTS under external/openglcts
directory. For more information see OpenGL / OpenGL ES CTS README.
ANGLE can be built for Android by following the instructions here.
The resulting ANGLE shared object libraries can be linked against and embedded into dEQP.apk
with the --angle-path
option. This will cause dEQP.apk
to use the ANGLE libraries for OpenGL ES calls, rather than the native drivers.
An ABI must be specified and the directory structure containing the ANGLE shared objects must match it so the build system can find the correct *.so
files.
Assuming ANGLE shared objects are generated into ~/chromium/src/out/Release/
and dEQP.apk
will be generated with --abis arm64-v8a
, issue the following commands:
cd ~/chromium/src/out/Release/ mkdir arm64-v8a && cd arm64-v8a cp ../lib*_angle.so .
The --angle-path ~/chromium/src/out/Release/
option can then be used to link against and embed the ANGLE shared object files. The full command would be:
python scripts/android/build_apk.py --sdk <path to Android SDK> --ndk <path to Android NDK> --abis arm64-v8a --angle-path ~/chromium/src/out/Release/