)]}'
{
  "commit": "6872f4af79edcc50925cf1e71556338965f7330d",
  "tree": "83529a716e11c8bdda398f3baa6a66205da74813",
  "parents": [
    "1c4481d807700f787f4f38aacd12629f218b0c0e"
  ],
  "author": {
    "name": "Peter McNeeley",
    "email": "petermcneeley@google.com",
    "time": "Tue Jun 10 09:30:43 2025 -0700"
  },
  "committer": {
    "name": "Dawn LUCI CQ",
    "email": "dawn-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Tue Jun 10 09:30:43 2025 -0700"
  },
  "message": "[dawn] Fallback to host memory for dma fd import\n\nSome devices may fail to find device local memory for these FD imports\n(likely from camera) when this occurs we can alternatively use host\nmemory even though there could be performance consequences. This\nissue was discovered on AMD.\n\nAMD device:\n(https://www.techpowerup.com/gpu-specs/amd-mendocino.g1022).\n\n\nFor the device in question the FD import allowed for memory types that\nhad the \u0027propertyFlags\u0027 with 0x0E and 0xCE.\n\nBoth memory types therefore support\nVK_MEMORY_PROPERTY_HOST_VISIBLE_BIT\nVK_MEMORY_PROPERTY_HOST_COHERENT_BIT\nVK_MEMORY_PROPERTY_HOST_CACHED_BIT\n\nBug: 422128949\nChange-Id: I320288343be9f9bfb676c45ec4a262383242d7c8\nReviewed-on: https://dawn-review.googlesource.com/c/dawn/+/245874\nReviewed-by: Brandon Jones \u003cbajones@chromium.org\u003e\nCommit-Queue: Peter McNeeley \u003cpetermcneeley@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b64e18c5ca1261a69fce175863adc96d59fa4f43",
      "old_mode": 33188,
      "old_path": "src/dawn/native/vulkan/external_memory/MemoryServiceImplementationDmaBuf.cpp",
      "new_id": "b76e1fceedee75f0e6038ccaf837563e5444d57d",
      "new_mode": 33188,
      "new_path": "src/dawn/native/vulkan/external_memory/MemoryServiceImplementationDmaBuf.cpp"
    }
  ]
}