)]}'
{
  "commit": "0282abf078c3353a178ab77a115828ce333181dd",
  "tree": "2241d625a31616f4d628bcb5315a0f8932921241",
  "parents": [
    "a1a88589dc982f9f8b6c717c2ac98dd71dd4353d"
  ],
  "author": {
    "name": "Alex Williamson",
    "email": "alex.williamson@redhat.com",
    "time": "Tue Nov 10 12:11:08 2015 -0700"
  },
  "committer": {
    "name": "Alex Williamson",
    "email": "alex.williamson@redhat.com",
    "time": "Tue Nov 10 12:11:08 2015 -0700"
  },
  "message": "vfio/pci: Hide device PCIe capability on non-express buses for PCIe VMs\n\nWhen we have a PCIe VM, such as Q35, guests start to care more about\nvalid configurations of devices relative to the VM view of the PCI\ntopology.  Windows will error with a Code 10 for an assigned device if\na PCIe capability is found for a device on a conventional bus.  We\nalso have the possibility of IOMMUs, like VT-d, where the where the\nguest may be acutely aware of valid express capabilities on physical\nhardware.\n\nSome devices, like tg3 are adversely affected by this due to driver\ndependencies on the PCIe capability.  The only solution for such\ndevices is to attach them to an express capable bus in the VM.\n\nSigned-off-by: Alex Williamson \u003calex.williamson@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8fadbcf682bba188b517146cce831d873b09059e",
      "old_mode": 33188,
      "old_path": "hw/vfio/pci.c",
      "new_id": "035007f707a1a76f9fd1caadb34bc8733ba6c8f6",
      "new_mode": 33188,
      "new_path": "hw/vfio/pci.c"
    }
  ]
}
