[PATCH 0/4] Add support for Vulkan shared memory in wine.

[Derek Lesho]

On 11/4/19 3:58 PM, Alexandre Julliard wrote:

> Derek Lesho <dlesho at codeweavers.com> writes:
>
>> Ah, I didn't see that, should have looked.  I can try to redo the
>> patchset using those in winevulkan.  One issue though is the use of
>> KMT handles, which are pretty much just resource IDs like PIDs or
>> TIDs.  How do propose we implement that without support in the
>> server?  Maybe we could use ConvertToGlobalHandle?  The issue then is
>> that the global handle isn't supposed to contain a reference to the
>> resource.
> It depends on how the IDs are supposed to behave,
Reading from 
https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/chap38.html#VkExternalMemoryHandleTypeFlagBits, 
VK_EXTERNAL_MEMORY_HANDLE_TYPE_OPAQUE_WIN32_KMT_BIT says that the ID is 
global, and does not contain a reference to the resource.  We could 
possibly use a shared memory region in winevulkan to map KMT handle IDs 
to the names of resource objects, since object names also don't hold a 
reference to the object.  What do you think about this solution?
>   but in any case
> ConvertToGlobalHandle() is a Win95 abomination that you should stay far
> away from ;-)
>