From 4c861cf22a63b892cec74bc132313dcd17d77584 Mon Sep 17 00:00:00 2001 From: Iago Toral Quiroga Date: Wed, 2 Nov 2022 10:53:59 +0100 Subject: [PATCH] v3dv: increase limit for active event objects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixes: ecb01d53fdb413121ce2 ("v3dv: refactor events") Fixes: dEQP-VK.api.command_buffers.execute_large_primary Reviewed-by: Alejandro Piñeiro Reviewed-by: Eric Engestrom Part-of: --- src/broadcom/vulkan/v3dv_event.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/broadcom/vulkan/v3dv_event.c b/src/broadcom/vulkan/v3dv_event.c index 411c4221082..529b88dba1d 100644 --- a/src/broadcom/vulkan/v3dv_event.c +++ b/src/broadcom/vulkan/v3dv_event.c @@ -231,8 +231,11 @@ v3dv_event_allocate_resources(struct v3dv_device *device) /* BO with event states. Make sure we always align to a page size (4096) * to ensure we use all the memory the kernel will allocate for the BO. + * + * CTS has tests that require over 8192 active events (yes, really) so + * let's make sure we allow for that. */ - const uint32_t bo_size = 4096; + const uint32_t bo_size = 3 * 4096; struct v3dv_bo *bo = v3dv_bo_alloc(device, bo_size, "events", true); if (!bo) { result = vk_error(device, VK_ERROR_OUT_OF_DEVICE_MEMORY);