panvk: Make sure push sets are reset when picked from the CommandPool
If we don't do that, we might end up with data from the previous user
of this set.
Fixes: 598a8d9d11 ("panvk: Collect allocated push sets at the command level")
Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
Reviewed-by: Rebecca Mckeever <rebecca.mckeever@collabora.com>
Reviewed-by: Mary Guillemard <mary.guillemard@collabora.com>
Reviewed-by: Lars-Ivar Hesselberg Simonsen <lars-ivar.simonsen@arm.com>
Reviewed-by: John Anthony <john.anthony@arm.com>
Acked-by: Erik Faye-Lund <erik.faye-lund@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30969>
This commit is contained in:
committed by
Marge Bot
parent
7f7e772bdf
commit
be96213634
@@ -83,6 +83,7 @@ panvk_per_arch(cmd_push_descriptors)(struct vk_command_buffer *vk_cmdbuf,
|
||||
list_first_entry(&pool->push_sets, struct panvk_push_set, base.node);
|
||||
list_del(&push_set->base.node);
|
||||
list_addtail(&push_set->base.node, &cmdbuf->push_sets);
|
||||
memset(push_set->descs, 0, sizeof(push_set->descs));
|
||||
} else {
|
||||
push_set = vk_zalloc(&pool->vk.alloc, sizeof(*push_set), 8,
|
||||
VK_SYSTEM_ALLOCATION_SCOPE_OBJECT);
|
||||
|
||||
Reference in New Issue
Block a user