)]}'
{
  "commit": "0069391d75fa42ea5e1109144bc08358a7814ee7",
  "tree": "583a31072d74d5696036e366bd5ef51bf4a3b767",
  "parents": [
    "fd57bb32eeed7fd4d2b8971ae8f6c39f4c5a70b4"
  ],
  "author": {
    "name": "Barret Rhoden",
    "email": "brho@cs.berkeley.edu",
    "time": "Mon Aug 14 12:06:28 2017 -0400"
  },
  "committer": {
    "name": "Barret Rhoden",
    "email": "brho@cs.berkeley.edu",
    "time": "Mon Aug 14 17:02:20 2017 -0400"
  },
  "message": "vmm: Use relative alarms for periodic LAPIC timers\n\nWith relative alarms, we\u0027ll try to inject another IPI in X ticks from now,\ninstead of X ticks from when we wanted the previous alarm to go off.\n\nIf the VMM is descheduled for a long time, perhaps due to being an SCP or\notherwise low-priority, the \"incremental\" alarms will build up, since we\ndon\u0027t run our alarm handler immediately.\n\nIf the guest clocks off the ticks, it\u0027ll have problems.  If that happens,\nwe can come up with something else.  I tested tinycore by giving it the\nperiod it wanted * 2, and it thought time passed correctly (date).\n\nSigned-off-by: Barret Rhoden \u003cbrho@cs.berkeley.edu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "584c95ddb5c73f59993162e2acd0d6cf1dcbbb1c",
      "old_mode": 33188,
      "old_path": "tests/vmm/vmrunkernel.c",
      "new_id": "023dfe4f32e5790cdaa635da3df72d11f0e24d20",
      "new_mode": 33188,
      "new_path": "tests/vmm/vmrunkernel.c"
    }
  ]
}