tree e55f520f42ddfa1aebdd44fec41359a2300183a3
parent 62e58ed31dc9711381fbe80817a89b51e9ff0686
author John Bauman <jbauman@google.com> 1556307352 -0700
committer John Bauman <jbauman@google.com> 1556322231 -0700

Add buffer creation support to VK_FUCHSIA_buffer_collection

On current systems any VMO can be imported as a buffer and it will work
just like a vulkan-created buffer, except that the client that doesn't
use vulkan has no idea whether cache operations are needed. However on
non-UMA systems it's possible that an arbitrary VMO could only be
imported in very limited ways, e.g. not attachable to a vertex buffer
or uniform buffer.

The sysmem interface supports creating buffer collections that aren't 2D
images, but are linear memory. We can extend the Vulkan buffer
collection interface to allow clients to request that.

The main differences between the buffer and image constraints interfaces
(besides the VkBufferCreateInfo parameter) are that VkFormatFeatureFlags
can be specified to require that certain operations (like
VK_FORMAT_FEATURE_STORAGE_TEXEL_BUFFER_ATOMIC_BIT) are supported. and
the minimum number of buffers in the collection are specified. The image
interface will be extended to support those features in the future.

Also updated Vulkan-Docs.diff to match the current versions:
Vulkan-Docs 3c0abef815a9ffe3d1b728bb383f132543e721b1
Vulkan-Hpp b4080fb4254dbc38fef7f71a262a08fe01cd964a

Change-Id: I76822922f646a5fdccd37b11f073b8555c17cd1e