)]}'
{
  "commit": "714e9affa8ae1d84007c8afde7bb10fef9cb883d",
  "tree": "2c772372dd0952aaa588a81b86652e792ca0fe5d",
  "parents": [
    "36e84d0c17102fa1c887d8c650a13ec08fca0ec0"
  ],
  "author": {
    "name": "Zhenzhong Duan",
    "email": "zhenzhong.duan@intel.com",
    "time": "Tue Nov 21 16:44:05 2023 +0800"
  },
  "committer": {
    "name": "Cédric Le Goater",
    "email": "clg@redhat.com",
    "time": "Tue Dec 19 19:03:38 2023 +0100"
  },
  "message": "vfio/iommufd: Add support for iova_ranges and pgsizes\n\nSome vIOMMU such as virtio-iommu use IOVA ranges from host side to\nsetup reserved ranges for passthrough device, so that guest will not\nuse an IOVA range beyond host support.\n\nUse an uAPI of IOMMUFD to get IOVA ranges of host side and pass to\nvIOMMU just like the legacy backend, if this fails, fallback to\n64bit IOVA range.\n\nAlso use out_iova_alignment returned from uAPI as pgsizes instead of\nqemu_real_host_page_size() as a fallback.\n\nSigned-off-by: Zhenzhong Duan \u003czhenzhong.duan@intel.com\u003e\nReviewed-by: Cédric Le Goater \u003cclg@redhat.com\u003e\nReviewed-by: Eric Auger \u003ceric.auger@redhat.com\u003e\nTested-by: Eric Auger \u003ceric.auger@redhat.com\u003e\nTested-by: Nicolin Chen \u003cnicolinc@nvidia.com\u003e\nSigned-off-by: Cédric Le Goater \u003cclg@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6d31aeac7bd8781a103328f8a438c011cdc2db1e",
      "old_mode": 33188,
      "old_path": "hw/vfio/iommufd.c",
      "new_id": "01b448e840581e0dd6d3df1897169665f79dcbe3",
      "new_mode": 33188,
      "new_path": "hw/vfio/iommufd.c"
    }
  ]
}