)]}'
{
  "commit": "5261bcfc854032f3ad28e79f4e6b9f27482467fc",
  "tree": "357d0470dc340ce1cd64465447087526ad1870a7",
  "parents": [
    "12f0d5b237499d53f9c0c1663c2bbe1dcc321056"
  ],
  "author": {
    "name": "Barret Rhoden",
    "email": "brho@cs.berkeley.edu",
    "time": "Fri Aug 18 11:23:09 2017 -0400"
  },
  "committer": {
    "name": "Barret Rhoden",
    "email": "brho@cs.berkeley.edu",
    "time": "Fri Aug 25 14:41:49 2017 -0400"
  },
  "message": "vmm: Allow vmm.h to include vmx.h\n\nThe higher-level vmm.h should include the more specific vmx.h.  Eventually,\nwe\u0027ll also include svm.h.  \u003d)  I\u0027ll need this for an upcoming change.\n\nNote this makes guest_pcore specific to Intel vs AMD.  I\u0027m not 100% on\nthat, but we do have a bunch of intel-specific things in it, such as the\nVMCS.  We might end up with guest_pcore being more generic and including\nvmx and svm structures, like vmx_guest_pcore, and all the vmx.h functions\ntake that as a parameter.\n\nSigned-off-by: Barret Rhoden \u003cbrho@cs.berkeley.edu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5384c4e7be2ff9c3a1f06119ce76e6109af7c36d",
      "old_mode": 33188,
      "old_path": "kern/arch/x86/vmm/intel/vmx.c",
      "new_id": "6f9cef73d184599427de49cb2b085a6ebd201e79",
      "new_mode": 33188,
      "new_path": "kern/arch/x86/vmm/intel/vmx.c"
    },
    {
      "type": "modify",
      "old_id": "b40bd6f3150edb04be610768c0433b7bbc6a9b5c",
      "old_mode": 33188,
      "old_path": "kern/arch/x86/vmm/intel/vmx.h",
      "new_id": "e6b50acf42f650d0f614fa08b9e4ab71570bd54c",
      "new_mode": 33188,
      "new_path": "kern/arch/x86/vmm/intel/vmx.h"
    },
    {
      "type": "modify",
      "old_id": "5c043fe0fcc0797820ad663113fbd106179320a5",
      "old_mode": 33188,
      "old_path": "kern/arch/x86/vmm/vmm.h",
      "new_id": "9ae840d2537b9159c29d95029823bc4e0428e7e5",
      "new_mode": 33188,
      "new_path": "kern/arch/x86/vmm/vmm.h"
    }
  ]
}