)]}'
{
  "commit": "336f308958d598f3db351bb7d94cc57b4b2d448d",
  "tree": "649cc76d5bac75dd040834fdfe1cb0345a0300e0",
  "parents": [
    "3016e60f8f715d2058a48e4956be994482c5e218"
  ],
  "author": {
    "name": "Zhenzhong Duan",
    "email": "zhenzhong.duan@intel.com",
    "time": "Tue Nov 21 16:44:13 2023 +0800"
  },
  "committer": {
    "name": "Cédric Le Goater",
    "email": "clg@redhat.com",
    "time": "Tue Dec 19 19:03:38 2023 +0100"
  },
  "message": "vfio/ap: Allow the selection of a given iommu backend\n\nNow we support two types of iommu backends, let\u0027s add the capability\nto select one of them. This depends on whether an iommufd object has\nbeen linked with the vfio-ap device:\n\nif the user wants to use the legacy backend, it shall not\nlink the vfio-ap device with any iommufd object:\n\n -device vfio-ap,sysfsdev\u003d/sys/bus/mdev/devices/XXX\n\nThis is called the legacy mode/backend.\n\nIf the user wants to use the iommufd backend (/dev/iommu) it\nshall pass an iommufd object id in the vfio-ap device options:\n\n -object iommufd,id\u003diommufd0\n -device vfio-ap,sysfsdev\u003d/sys/bus/mdev/devices/XXX,iommufd\u003diommufd0\n\nSuggested-by: Alex Williamson \u003calex.williamson@redhat.com\u003e\nSigned-off-by: Zhenzhong Duan \u003czhenzhong.duan@intel.com\u003e\nReviewed-by: Matthew Rosato \u003cmjrosato@linux.ibm.com\u003e\nReviewed-by: Cédric Le Goater \u003cclg@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": "bbf69ff55ae8a922d0ab6d6f966a9a2283cdd2a3",
      "old_mode": 33188,
      "old_path": "hw/vfio/ap.c",
      "new_id": "80629609aebbff9156f78c9bbde5dc6c293ac84e",
      "new_mode": 33188,
      "new_path": "hw/vfio/ap.c"
    }
  ]
}