Intel Celeron N2840
Mesa DRI Intel(R) Bay Trail (0xf31)

For quite a time the DXVK wrapper have been completely unusable for me because of alot DxvkMemoryAllocator: Memory allocation failed errors. Most games renderings are pitch black, with rare exceptions. I put some efforts to investigate into this showstopper and now i think has found the clue.

According to Mesa sources (intel/vulkan/anv_device.c):

  if (device->info.has_llc) {
     /* Big core GPUs share LLC with the CPU and thus one memory type can be
      * both cached and coherent at the same time.
      */
     device->memory.types[type_count++] = (struct anv_memory_type) {
        .propertyFlags = VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT |
                         VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT |
                         VK_MEMORY_PROPERTY_HOST_COHERENT_BIT |
                         VK_MEMORY_PROPERTY_HOST_CACHED_BIT,
        .heapIndex = heap,
        .valid_buffer_usage = valid_buffer_usage,
     };
  } else {
     /* The spec requires that we expose a host-visible, coherent memory
      * type, but Atom GPUs don't share LLC. Thus we offer two memory types
      * to give the application a choice between cached, but not coherent and
      * coherent but uncached (WC though).
      */
     device->memory.types[type_count++] = (struct anv_memory_type) {
        .propertyFlags = VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT |
                         VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT |
                         VK_MEMORY_PROPERTY_HOST_COHERENT_BIT,
        .heapIndex = heap,
        .valid_buffer_usage = valid_buffer_usage,
     };
     device->memory.types[type_count++] = (struct anv_memory_type) {
        .propertyFlags = VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT |
                         VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT |
                         VK_MEMORY_PROPERTY_HOST_CACHED_BIT,
        .heapIndex = heap,
        .valid_buffer_usage = valid_buffer_usage,
     };
  }

So, when got unlucky GPU you cannot have HOST_COHERENT_BIT and HOST_CACHED_BIT flags both set! Having this in mind i made a proof of the concept code insertion in DxvkMemoryAllocator::tryAlloc

	if ((flags &  (VK_MEMORY_PROPERTY_HOST_COHERENT_BIT | VK_MEMORY_PROPERTY_HOST_CACHED_BIT))
               == (VK_MEMORY_PROPERTY_HOST_COHERENT_BIT | VK_MEMORY_PROPERTY_HOST_CACHED_BIT))
		flags &= ~VK_MEMORY_PROPERTY_HOST_CACHED_BIT;

Perhaps, i did it ugly way but it indeed fixed the problem, or at least, sweep it under the carpet. No more errors of THAT kind, backgrounds and models are fine, textures in place. There are still some known BayTrail-vulkan related visual glitches and issues in games because of unfinished drivers but that's irrelevant to DXVK.

The essential from DXVK logs seem to proof the findings:

info: DXVK: v1.0
warn: OpenVR: Failed to locate module
info: Enabled instance extensions:
info: VK_KHR_get_physical_device_properties2
info: VK_KHR_surface
info: VK_KHR_win32_surface
info: Intel(R) Bay Trail:
info: Driver: 18.3.3
info: Vulkan: 1.1.90
info: Memory Heap[0]:
info: Size: 1536 MiB
info: Flags: 0x1
info: Memory Type[0]: Property Flags = 0x7
info: Memory Type[1]: Property Flags = 0xb

Yes, those property flags in logs again. I hope the above will help to get Intel Atoms in line.