Re: [PATCH v3 0/7] MR5128: winevulkan: Use VK_EXT_map_memory_placed for memory mapping on wow64.

[Georg Lehmann (＠DadSchoorse)]

Georg Lehmann (@DadSchoorse) commented about dlls/winevulkan/vulkan.c:
>          instance->funcs.p_vkEnumeratePhysicalDeviceGroupsKHR, count, properties);
>
> }
>
> +void wine_vkGetPhysicalDeviceFeatures2KHR(VkPhysicalDevice phys_dev_handle, VkPhysicalDeviceFeatures2 *features)
> +{
> - struct wine_phys_dev *phys_dev = wine_phys_dev_from_handle(phys_dev_handle);
> - VkPhysicalDeviceMapMemoryPlacedFeaturesEXT *map_placed_features;
> -
> - phys_dev->instance->funcs.p_vkGetPhysicalDeviceFeatures2KHR(phys_dev->host_physical_device, features);
> -
> - map_placed_features = find_next_struct(features->pNext,
> -
>                                       VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MAP_MEMORY_PLACED_PROPERTIES_EXT);
> - if (map_placed_features)
> - {
> -
>    map_placed_features->memoryMapPlaced = VK_FALSE;
> -
>    map_placed_features->memoryMapRangePlaced = VK_FALSE;

If we don't support either of these features, why support the extension at all? Adding it to `UNEXPOSED_EXTENSIONS` seems like the saner thing to do.