| commit | f31b71637586c7b32756b82c6d33914cd27c625b | [log] [tgz] |
|---|---|---|
| author | Ricardo Garcia <rgarcia@igalia.com> | Wed Apr 30 10:53:49 2025 |
| committer | Lorenzo Dal Col <lorenzo@khronosgroup.org> | Fri May 09 10:24:51 2025 |
| tree | 3e86f1c3114467a7316a359dd9b90398d9c9d009 | |
| parent | 8603b0610080ae8df68a78eb2aa5a54b41af02b8 [diff] |
Test enabling FSR explicitly and implicitly New test that creates a single pipeline using dynamic rendering and FSR, binds it and uses it in two dynamic render passes. The pipeline has a rate of 2x2 and combiner ops KEEP,REPLACE. This means the attachment rate always applies. The first dynamic render pass uses an FSR attachment that sets the rate to 1x1 explicitly. The second dynamic render pass skips the FSR attachment. In its absence, the rate should still be 1x1, instead of applying the pipeline rate of 2x2. Quoting the specification in its description of VkRenderingFragmentShadingRateAttachmentInfoKHR: > This structure can be included in the pNext chain of VkRenderingInfo > to define a fragment shading rate attachment. If imageView is > VK_NULL_HANDLE, or if this structure is not specified, the > implementation behaves as if a valid shading rate attachment was > specified with all texels specifying a single pixel per fragment. New test: dEQP-VK.fragment_shading_rate.dynamic_rendering.primary_cmd_buff.monolithic.misc.explicit_and_implicit_enable VK-GL-CTS issue: 5720 Components: Vulkan Change-Id: I6634327b7cd652b1459bf451f797b4140568d475
This repository contains Khronos Conformance Testing Suite called VK-GL-CTS which originated from dEQP (drawElements Quality Program). VK-GL-CTS contains tests for several graphics APIs, including OpenGL, OpenGL ES, EGL, Vulkan, and Vulkan SC.
Up-to-date documentation for VK-GL-CTS is available at:
The .qpa logs generated by the conformance tests may contain embedded PNG images of the results. These can be viewed with scripts/qpa_image_viewer.html, by opening the file with a web browser and following its instructions, or using 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.
When configuring the source code of VK-GL-CTS for running either Vulkan Conformance Tests or OpenGL(ES) Conformance Tests as described above, CMake will generate build files that, by default on desktop platforms, will build every possible project binary. This may be undesirable due the amount of time and disk space needed to perform the build.
One way of selecting only a subset of the targets to be built is using CMake's target selection mechanism. For example, the following command will only build deqp-vk, the main Vulkan Conformance Tests binary:
cmake --build BUILD_DIRECTORY --target deqp-vk
When building only a subset of targets is the preferred default behavior for a given working copy or build directory, there's a second target selection mechanism that can be used to avoid passing the --target option every time: the SELECTED_BUILD_TARGETS CMake option. If set to a non-empty value, only the targets listed in that configuration option, separated by spaces, will be built.
For example, passing -DSELECTED_BUILD_TARGETS="deqp-vk deqp-vksc" when configuring the project will make cmake --build BUILD_DIRECTORY act as if it had been passed --target deqp-vk --target deqp-vksc as additional arguments.
IMPORTANT: Target subset selection may not have been thoroughly tested in all enviroments and situations, and it does not replace the instructions given for the purposes of creating a conformance submission.
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/
In order to run the vulkan video decode test suite, you'll need to run the script external/fetch_video_decode_samples.py prior building and running any test suite such as dEQP-VK.video.decode.*. It will download the video clips in external/vulkancts/data/vulkan/video.
To run the vulkan video encode test suite, you'll need to run the script external/fetch_video_encode_samples.py prior building and running any test suite such as dEQP-VK.video.encode.*. It will download the video clips in external/vulkancts/data/vulkan/video.