)]}'
{
  "commit": "a45863bda90daa8ec39e5a312b9734fd4665b016",
  "tree": "47347d0061b7ca92021d3bd91041fcb52e31de28",
  "parents": [
    "19fb2c36e2475a2c68e7287e0e089d858dd7cc50"
  ],
  "author": {
    "name": "Bharata B Rao",
    "email": "bharata@linux.vnet.ibm.com",
    "time": "Thu Jul 02 16:23:20 2015 +1000"
  },
  "committer": {
    "name": "Alexander Graf",
    "email": "agraf@suse.de",
    "time": "Tue Jul 07 17:44:52 2015 +0200"
  },
  "message": "xics_kvm: Don\u0027t enable KVM_CAP_IRQ_XICS if already enabled\n\nWhen supporting CPU hot removal by parking the vCPU fd and reusing\nit during hotplug again, there can be cases where we try to reenable\nKVM_CAP_IRQ_XICS CAP for the vCPU for which it was already enabled.\nIntroduce a boolean member in ICPState to track this and don\u0027t\nreenable the CAP if it was already enabled earlier.\n\nRe-enabling this CAP should ideally work, but currently it results in\nkernel trying to create and associate ICP with this vCPU and that\nfails since there is already an ICP associated with it. Hence this\npatch is needed to work around this problem in the kernel.\n\nThis change allows CPU hot removal to work for sPAPR.\n\nSigned-off-by: Bharata B Rao \u003cbharata@linux.vnet.ibm.com\u003e\nReviewed-by: David Gibson \u003cdavid@gibson.dropbear.id.au\u003e\nSigned-off-by: David Gibson \u003cdavid@gibson.dropbear.id.au\u003e\nSigned-off-by: Alexander Graf \u003cagraf@suse.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ea886dac7b30f897350d10a76c9eb05416a87f85",
      "old_mode": 33188,
      "old_path": "hw/intc/xics_kvm.c",
      "new_id": "d58729cfae9142198ef13af6318427ef87f66d0c",
      "new_mode": 33188,
      "new_path": "hw/intc/xics_kvm.c"
    },
    {
      "type": "modify",
      "old_id": "a214dd7f28172caab6c110b34bbce41243e2d8f5",
      "old_mode": 33188,
      "old_path": "include/hw/ppc/xics.h",
      "new_id": "355a96623c70940d9dd21bd4456d34c0902c6b5c",
      "new_mode": 33188,
      "new_path": "include/hw/ppc/xics.h"
    }
  ]
}