| ca85fdbae6b9cbf7bfa0c4be24c8de7faa8007dd |
|
02-Nov-2017 |
Vikram Kushwaha <vkushwaha@nvidia.com> |
Fix image layout transitions for peer Image
When SFR/AFR copies are performed by peer device into
the primary device's render target, the image layout transitions are
also being performed by peer device.
This is only correct if GENERIC_SRC\GENERIC_DST feature flags
are supported.
VK-GL-CTS issue: 807
Change-Id: Ie3ffe6a68976ad644de12bd2c923cd0a34defe5f
Affects: dEQP-VK.device_group.*
Components: Vulkan
/external/deqp/external/vulkancts/modules/vulkan/device_group/vktDeviceGroupRendering.cpp
|
| 5b36c7b5b93b470ed4b20199976a58a625471a63 |
|
18-Oct-2017 |
Vikram Kushwaha <vkushwaha@nvidia.com> |
Do not use SFR bindings when device group has 1 device
As per the spec, when device group has 1 device:
sfrRects must not be specified
image create flag should not contain the BIND_SFR_BIT
Also use peer memory reads if VK_PEER_MEMORY_FEATURE_COPY_SRC_BIT
is supported. This saves an additionaly copy in the test.
VK-GL-CTS issue: 779
Change-Id: Ic316fc8858886f99156dc1b9c0a0810b3f48e714
Affects: dEQP-VK.device_group.sfr*
Components: Vulkan
/external/deqp/external/vulkancts/modules/vulkan/device_group/vktDeviceGroupRendering.cpp
|
| 69de8d3f5ee3b1874173210a9b88831b54e5c6f9 |
|
03-Jun-2017 |
Vikram Kushwaha <vkushwaha@nvidia.com> |
Add tests for multi GPU (device group)
Device Group tests may use multiple physical devices for rendering.
If there are 2 or more physical devices in a device group, tests
are looped through all physical devices, 2 at a time.
If there is only 1 physical device, the test is only run on it.
Primarily, there are 2 main test modes:
AFR(Alternate frame rendering) and SFR(Split frame rendering)
AFR: A frame(tessellated or filled sphere) is drawn by one of the
physical devices ['i'+1] and copied to the render target of phys
device 'i' which then does a check against reference image.
SFR: Each half of the frame is drawn by a physical device 'i'
and 'i+1'%(num phys devices), then phys device 'i' does a check
against reference image.
SFR and AFR have 6 modes each:
1. Rendering a triangle with render target in device memory
2. Rendering a triangle with render target in host memory
3. dedicated memory allocations for buffers and render target
4. Peer fetching of vertex, uniform and sbo data, (ith physical
device fetches attributes from (i+1)%(num phys devices)th peer device
5. Render a tessellated sphere
6. Render a tesslated sphere in line fill mode
For validation, the rendering is either compared against a system
renderer(for triangle) or compared against a stored png (in case of
a tessellated sphere)
New tests:
dEQP-VK.device_group.sfr*
dEQP-VK.device_group.afr*
Components: Vulkan
VK-GL-CTS issue: 110
Change-Id: Ibace53a1c3be610798925a339a763a808f9f76b9
/external/deqp/external/vulkancts/modules/vulkan/device_group/vktDeviceGroupRendering.cpp
|