)]}'
{
  "commit": "d69f819e8aac4ebc5669027d1fefbe01ddfc3d27",
  "tree": "5151da4d18bfd8e291f5f99676ebeeb54843bdce",
  "parents": [
    "85822cfce9f883c756100189c6fe9b0b551a692a"
  ],
  "author": {
    "name": "Kent McLeod",
    "email": "Kent.Mcleod@data61.csiro.au",
    "time": "Tue May 05 10:28:30 2020 +1000"
  },
  "committer": {
    "name": "Kent McLeod",
    "email": "Kent.Mcleod@data61.csiro.au",
    "time": "Tue May 05 10:28:30 2020 +1000"
  },
  "message": "cross_vm_connection: Round up event BAR size\n\nAs our vpci device doesn\u0027t support emulating remapping of device\nresource physical addresses by the guest, we need to create our devices\nin a way that Linux won\u0027t decide to remap them. This means making each\nBAR the same size.  For Cross-VM connectors we have a dataport and event\nresource. We describe both as being the size of the dataport, but only\ncreate a single page for the event port.  This assumes that the guest\nwill only access the first word of the event port for signalling events\nand we have a large enough address range to spend on making the event\nresource as large as the dataport one.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c5f4a24cc319dcc03a90076892e4093b5c007a08",
      "old_mode": 33188,
      "old_path": "libsel4vmmplatsupport/src/drivers/cross_vm_connection.c",
      "new_id": "d875175215f62c27ce2aa030479ea5fc6fd6ed5c",
      "new_mode": 33188,
      "new_path": "libsel4vmmplatsupport/src/drivers/cross_vm_connection.c"
    }
  ]
}