)]}'
{
  "commit": "b4ad84a454f6532d0a7de910dce4bd97a26d1340",
  "tree": "348fd14c5d874eb7afc2ef690c78738f413111b7",
  "parents": [
    "a252304904aa631f8d01b9b2827454665ba07050"
  ],
  "author": {
    "name": "Barret Rhoden",
    "email": "brho@cs.berkeley.edu",
    "time": "Tue Dec 12 13:24:02 2017 -0500"
  },
  "committer": {
    "name": "Barret Rhoden",
    "email": "brho@cs.berkeley.edu",
    "time": "Tue Dec 12 13:24:02 2017 -0500"
  },
  "message": "vmm: Check VPPR and interrupt-window-blocking with RVI\n\nWe had been checking just the full byte of RVI.  However, that is not what\nthe hardware will treat as a condition to trigger an interrupt in the\nguest.\n\nI didn\u0027t have a specific problem with this, but it popped up as a potential\nissue when I was working on IPIs.\n\nNote that vectors less than 16 in RVI won\u0027t trigger a wakeup, which is in\naccordance with the SDM\u0027s algorithm.  The only time I\u0027ve seen the RVI field\nless than 16 so far is during an INIT/SIPI.\n\nSigned-off-by: Barret Rhoden \u003cbrho@cs.berkeley.edu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "dfef6c06c17364d7581e09c8c41b47cfcf032efc",
      "old_mode": 33188,
      "old_path": "user/vmm/vmexit.c",
      "new_id": "bb175599790b6ea2a1050f0ff30d62e5d0dd5183",
      "new_mode": 33188,
      "new_path": "user/vmm/vmexit.c"
    }
  ]
}