[PATCH v13 3/4] winevulkan: Implement VK_KHR_external_memory_win32 for buffers.

Derek Lesho dlesho at codeweavers.com
Mon Aug 2 08:56:08 CDT 2021

On 7/22/21 1:33 AM, Zebediah Figura (she/her) wrote:

> I'm still not convinced that this is the right way to implement this.
What, in specific, is wrong with the way this patch is implemented. In 
previous mail I mentioned how this patch mostly just sets up the 
winevulkan infrastructure for converting the pNext chain entries for 
importing and exporting resources, and accepting it doesn't imply a 
value-judgement on any potential path forwards in regards to storing 
metadata or interop with other APIs.  Is the problem you have that we 
use EXTERNAL_MEMORY_fd at all?  If I'm not mistaken, we'd be using it in 
any path we decide to go down.  (the wineserver object, whatever it may 
be, will hold an fd pointing to the underlying resource).

More information about the wine-devel mailing list