)]}'
{
  "commit": "55cb8cd45e0600df1473489518d7f12ce1bbe973",
  "tree": "10e0d7301cca3b6511018703a4c1cb7f4645cb36",
  "parents": [
    "1d4610527bc71d3f9eea520fc51a02d54f79dcd0"
  ],
  "author": {
    "name": "Konrad Rzeszutek Wilk",
    "email": "konrad.wilk@oracle.com",
    "time": "Wed Feb 16 13:43:04 2011 -0500"
  },
  "committer": {
    "name": "Konrad Rzeszutek Wilk",
    "email": "konrad.wilk@oracle.com",
    "time": "Fri Feb 18 09:26:37 2011 -0500"
  },
  "message": "pci/xen: Use xen_allocate_pirq_msi instead of xen_allocate_pirq\n\nxen_allocate_pirq -\u003e xen_map_pirq_gsi -\u003e PHYSDEVOP_alloc_irq_vector IFF\nxen_initial_domain() in addition to the kernel side book-keeping side of\nthings (set chip and handler, update irq_info etc) whereas\nxen_allocate_pirq_msi just does the kernel book keeping.\n\nAlso xen_allocate_pirq allocates an IRQ in the 1-1 GSI space whereas\nxen_allocate_pirq_msi allocates a dynamic one in the \u003eGSI IRQ space.\n\nAll of this is uneccessary as this code path is only executed\nwhen we run as a domU PV guest with an MSI/MSI-X PCI card passed in.\nHence we can jump straight to allocating an dynamic IRQ (and\nbinding it to the proper PIRQ) and skip the rest.\n\nIn short: this change is a cosmetic one.\n\nReviewed-by: Ian Campbell \u003cIan.Campbell@citrix.com\u003e\nReviewed-by: Stefano Stabellini \u003cstefano.stabellini@eu.citrix.com\u003e\nSigned-off-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "25cd4a07d09f78cbe850733f0d2d36d98fe5d176",
      "old_mode": 33188,
      "old_path": "arch/x86/pci/xen.c",
      "new_id": "6432f751ee4fd54b35b6e6a4d49c5601ab8e83c3",
      "new_mode": 33188,
      "new_path": "arch/x86/pci/xen.c"
    }
  ]
}