diff options
| author | Jean-François Marquis <jfmarquis@gmail.com> | 2017-10-30 18:14:15 -0400 |
|---|---|---|
| committer | Mark Lobodzinski <mark@lunarg.com> | 2017-11-03 09:19:22 -0600 |
| commit | 9ef531dfcde2c23bd3d8008c36439ad4f6aa79ce (patch) | |
| tree | e1f93206874262e3aca56b6119437ba284aaa502 /scripts | |
| parent | 9a8815136e5d086adac39f6e015c6e4728e5dc88 (diff) | |
| download | usermoji-9ef531dfcde2c23bd3d8008c36439ad4f6aa79ce.tar.xz | |
layers: Protect GetImage/BufferMemRqmts map access
Lock 'global_lock' while looking for IMAGE_STATE/BUFFER_STATE in
GetBufferMemoryRequirements/GetImageMemoryRequirements. This is needed
because other threads could add/remove other VkImage handles to/from
the maps concurrently. The specs say the VkImage must be externally
synchronized, but this doesn't cover the internals of the layers about
VkImages in general. vkCreateImage, vkDestroyImage and
vkBindImageMemory/vkBindBufferMemory correctly lock 'global_lock'.
Change-Id: I93cb00c9a7f99efc927da52e42103ab72516397e
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions