device_generic_goldfish-opengl, branch sdk-release

Snap for 6877830 from 16dbce711df7ed86dd4f2960af335c461c0d6127 to sdk-release

2020-10-01T20:29:35+00:00

Change-Id: I84aa10c1578e6da24300aa015c749e4a39fdcd36

Revert "Switch to vk_icdInitializeOpenInNamespaceCallback"

2020-10-01T14:09:51+00:00

This reverts commit 4b18053d54987324b93870c34d275526035cfc44.

Reason for revert: Fails Fuchsia CQ because some prebuilts have not yet adopted the new Vulkan Loader. Will restore ASAP.

Change-Id: I7fcf5a4c765a8fb6bec262fabe7d08759abf34b2

Switch to vk_icdInitializeOpenInNamespaceCallback

2020-09-30T21:11:04+00:00

fxb/60206

Change-Id: I95b40de991f665223d38327ea21d31fc4b86a688

fuchsia: Set sysmem constraints only if format/tiling/usage valid on host.

2020-09-18T20:44:16+00:00

Host Vulkan driver may not support some specific format, tiling and
image usage combinations. Before guest ICD set up sysmem buffer
collection constraints, guest needs to verify the image properties
to ensure that this works on host Vulkan driver, otherwise it may
cause further issues with the ColorBuffer/guest Vulkan image.

TEST=chromium test on FEMU.

Change-Id: I391c564a39cfecf35e8e2ca6486f8e35bed5ee96

Use VkEncoder.inl.* instead of letting it be generated (guest)

2020-09-17T22:15:10+00:00

Change-Id: I1f7e22406dcb93f60afe94b9e3f6b4e74706479a

Merge "Don't try to do robust buffer access checks on non-linked attrib indices"

2020-09-17T22:14:48+00:00

Don't try to do robust buffer access checks on non-linked attrib indices

2020-09-17T03:33:43+00:00

There's no danger from allowing out of bounds access there if the shader
program does nothing with it.

Don't upload client arrays in that case either.

Change-Id: Ic356a75d28fcf880608f3d44ca123bba18913c65

vulkan: Use heap type to determine buffer collection type

2020-09-17T01:51:36+00:00

Instead of using coherency domain, goldfish should use |heap|
properties to determine the buffer collection type, and reject
all the non-goldfish buffer collections.

TEST=chromium on core.qemu-x64

Change-Id: Ia8d11519f89ce9e880525a188c327dba7cc286dc

Merge "vulkan: Support imported host-visible memory on Fuchsia."

2020-09-16T21:15:45+00:00

vulkan: Support imported host-visible memory on Fuchsia.

2020-09-16T19:35:00+00:00

This change adds required logic to support GOLDFISH_HOST_VISIBLE
heap and host-visible external memory allocation on Fuchsia.

It includes the following parts:

(1) BufferCollectionConstraints:

    Now both DEVICE_LOCAL and HOST_VISIBLE domain can be added to
    the buffer_constraints.

    Currently, the domain of buffer collection constraints set in
    "setBufferCollectionConstraints(collection, image_create_info)"
    suppots both Heap types; other sysmem participants need to specify
    buffer memory constraints (cpu_supported, ram_supported,
    inaccessible_supported) or directly specify HeapType to choose
    the actual Heap.

(2) Stride:

    The stride of the Image will be determined by host GPU using
    vkGetLinearImageLayoutGOOGLE() method; other sysmem participants
    should NOT specify stride / offset requirements.

(3) Usage:

    Currently the VMO and VMAR rights is completely determined by the
    VkImage usage. It is writeable only when the usages in their
    ImageCreateInfo contains some writeable types (e.g. TRANSFER_DST).

TEST=terminal and spinning-square-rs on FEMU (software-gpu).

     Both apps uses host rendering and allocates image buffers from sysmem
     host-visible Heap.

Bug: fuchsia:54153
Change-Id: I8268b5fbe6d8a547bde2b02537130530849831f7