mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-01-10 12:30:11 +01:00
radv: Disable EXT BDA capture and replay.
Spec allows calling VkBufferGetDeviceAddressInfo without binding to memory:
VUID-VkBufferDeviceAddressInfo-buffer-02600
If buffer is non-sparse and was not created with the VK_BUFFER_CREATE_DEVICE_ADDRESS_CAPTURE_REPLAY_BIT flag, then it must be bound completely and contiguously to a single VkDeviceMemory object
Which we can only do by making it sparse unconditionally, which feels very wrong to me for a capture & replay extension as that significantly impacts execution.
Current theory is that this was only intended for the EXT and not the core functionality. As such, let's disable capture using the EXT.
Cc: mesa-stable
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31140>
(cherry picked from commit c8c354d9c3)
This commit is contained in:
parent
a1689bcea4
commit
ce52e7b1ef
2 changed files with 2 additions and 2 deletions
|
|
@ -4,7 +4,7 @@
|
|||
"description": "radv: Disable EXT BDA capture and replay.",
|
||||
"nominated": true,
|
||||
"nomination_type": 0,
|
||||
"resolution": 0,
|
||||
"resolution": 1,
|
||||
"main_sha": null,
|
||||
"because_sha": null,
|
||||
"notes": null
|
||||
|
|
|
|||
|
|
@ -983,7 +983,7 @@ radv_physical_device_get_features(const struct radv_physical_device *pdev, struc
|
|||
.descriptorBindingAccelerationStructureUpdateAfterBind = true,
|
||||
|
||||
/* VK_EXT_buffer_device_address */
|
||||
.bufferDeviceAddressCaptureReplayEXT = true,
|
||||
.bufferDeviceAddressCaptureReplayEXT = false,
|
||||
|
||||
/* VK_KHR_shader_subgroup_uniform_control_flow */
|
||||
.shaderSubgroupUniformControlFlow = true,
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue