Skip to content
Snippets Groups Projects
Commit daaf7efb authored by Bas Nieuwenhuizen's avatar Bas Nieuwenhuizen
Browse files

radv: Don't segfault when exporting an image which hasn't been bound yet.


The image is set on Memory allocation already, but the image doesn't
have to have the BindImageMemory called yet. Luckily, we know offset
within a BO has to be 0 for dedicated allocations, so we can just
use the dummy 0 in the address calaculations.

Fixes CTS test dEQP-VK.api.external.memory.opaque_fd.dedicated.image.export_bind_import_bind

Signed-off-by: default avatarBas Nieuwenhuizen <basni@google.com>
Fixes: b7082970 "radv: Implement VK_KHR_external_memory"
Reviewed-by: default avatarDave Airlie <airlied@redhat.com>
parent ea08a296
No related branches found
No related tags found
No related merge requests found
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment