)]}'
{
  "commit": "2aff696b10d16ef09dc5a2c953ceccbf6d38f744",
  "tree": "2d200966bddd1452fd91438db24ca1cee2fb289d",
  "parents": [
    "ddf0fd9ae1fd1ff95489763b37a483adb3cd5907"
  ],
  "author": {
    "name": "David Woodhouse",
    "email": "dwmw@amazon.co.uk",
    "time": "Fri Dec 16 00:03:21 2022 +0000"
  },
  "committer": {
    "name": "David Woodhouse",
    "email": "dwmw@amazon.co.uk",
    "time": "Wed Mar 01 09:07:50 2023 +0000"
  },
  "message": "hw/xen: Support HVM_PARAM_CALLBACK_TYPE_PCI_INTX callback\n\nThe guest is permitted to specify an arbitrary domain/bus/device/function\nand INTX pin from which the callback IRQ shall appear to have come.\n\nIn QEMU we can only easily do this for devices that actually exist, and\neven that requires us \"knowing\" that it\u0027s a PCMachine in order to find\nthe PCI root bus — although that\u0027s OK really because it\u0027s always true.\n\nWe also don\u0027t get to get notified of INTX routing changes, because we\ncan\u0027t do that as a passive observer; if we try to register a notifier\nit will overwrite any existing notifier callback on the device.\n\nBut in practice, guests using PCI_INTX will only ever use pin A on the\nXen platform device, and won\u0027t swizzle the INTX routing after they set\nit up. So this is just fine.\n\nSigned-off-by: David Woodhouse \u003cdwmw@amazon.co.uk\u003e\nReviewed-by: Paul Durrant \u003cpaul@xen.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6b0bdba65df39011148046686f1741413782aaba",
      "old_mode": 33188,
      "old_path": "hw/i386/kvm/xen_evtchn.c",
      "new_id": "f39b751ff99919f828bc54e56f0a141eb9d0e807",
      "new_mode": 33188,
      "new_path": "hw/i386/kvm/xen_evtchn.c"
    },
    {
      "type": "modify",
      "old_id": "b52617df549027d98b42e663877d81f81f1a1d3d",
      "old_mode": 33188,
      "old_path": "target/i386/kvm/xen-emu.c",
      "new_id": "9e22c9fa025f881df8bc9b2af8804da3126520c0",
      "new_mode": 33188,
      "new_path": "target/i386/kvm/xen-emu.c"
    }
  ]
}