From e34dc0840bf318cdd6524bcb8671ae4b849e4039 Mon Sep 17 00:00:00 2001 From: Mike Blumenkrantz Date: Mon, 19 Apr 2021 18:28:13 -0400 Subject: zink: use cached memory for staging resources I think at one point before staging resource flagging was less reliable this method made sense, but now it's worse Fixes: 6ff6d01c377 ("zink: don't use cached mem for staging resources") Reviewed-by: Adam Jackson Part-of: --- src/gallium/drivers/zink/zink_resource.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/gallium/drivers/zink/zink_resource.c b/src/gallium/drivers/zink/zink_resource.c index efd7a6e5df8..b1906ec2815 100644 --- a/src/gallium/drivers/zink/zink_resource.c +++ b/src/gallium/drivers/zink/zink_resource.c @@ -454,7 +454,7 @@ resource_object_create(struct zink_screen *screen, const struct pipe_resource *t if (templ->flags & PIPE_RESOURCE_FLAG_MAP_COHERENT || templ->usage == PIPE_USAGE_DYNAMIC) flags |= VK_MEMORY_PROPERTY_HOST_COHERENT_BIT; else if (!(flags & VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT) && - templ->usage != PIPE_USAGE_STAGING) + templ->usage == PIPE_USAGE_STAGING) flags |= VK_MEMORY_PROPERTY_HOST_CACHED_BIT; VkMemoryAllocateInfo mai = {}; -- cgit v1.2.3