diff options
| author | Lynne <dev@lynne.ee> | 2020-05-10 23:53:39 +0300 |
|---|---|---|
| committer | Lynne <dev@lynne.ee> | 2020-05-11 01:20:49 +0300 |
| commit | 875c1707e5f6287a6dabc7bc2dc5e1a9f3dc811b (patch) | |
| tree | 59a6394ef350c6fd6fc8ccec382eea7e51104bca /libavutil/hwcontext_vulkan.h | |
| parent | 7c080dc190ac1d85de1ca873347d0ac8855985e0 (diff) | |
hwcontext_vulkan: create all images with concurrent sharing mode
As it turns out, we were already assuming and treating all images as if they had
concurrent access mode. This just changes the flag to CONCURRENT, which has less
restrictions than EXCLUSIVE, and fixed validation messages on machines with
multiple queues.
The validation layer didn't pick this up because the machine I was testing on
had only a single queue.
Diffstat (limited to 'libavutil/hwcontext_vulkan.h')
| -rw-r--r-- | libavutil/hwcontext_vulkan.h | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/libavutil/hwcontext_vulkan.h b/libavutil/hwcontext_vulkan.h index 7f921d7af1..9a42790e41 100644 --- a/libavutil/hwcontext_vulkan.h +++ b/libavutil/hwcontext_vulkan.h @@ -119,6 +119,10 @@ typedef struct AVVulkanFramesContext { * All frames, imported or allocated, will be created with the * VK_IMAGE_CREATE_ALIAS_BIT flag set, so the memory may be aliased if needed. * + * If all three queue family indices in the device context are the same, + * images will be created with the EXCLUSIVE sharing mode. Otherwise, all images + * will be created using the CONCURRENT sharing mode. + * * @note the size of this structure is not part of the ABI, to allocate * you must use @av_vk_frame_alloc(). */ |