)]}'
{
  "commit": "b8cc45d6a6f7b6607d5c55817d674f3e5f92ff70",
  "tree": "6c48088104c0a82dafed244598b8154613447302",
  "parents": [
    "cdea50ede1b8a2efe989fafc57260053b180219f"
  ],
  "author": {
    "name": "Glauber Costa",
    "email": "glommer@redhat.com",
    "time": "Thu Feb 03 14:19:53 2011 -0500"
  },
  "committer": {
    "name": "Marcelo Tosatti",
    "email": "mtosatti@redhat.com",
    "time": "Mon Feb 14 12:39:46 2011 -0200"
  },
  "message": "kvm: make tsc stable over migration and machine start\n\nIf the machine is stopped, we should not record two different tsc values\nupon a save operation. The same problem happens with kvmclock.\n\nBut kvmclock is taking a different diretion, being now seen as a separate\ndevice. Since this is unlikely to happen with the tsc, I am taking the\napproach here of simply registering a handler for state change, and\nusing a per-CPUState variable that prevents double updates for the TSC.\n\nSigned-off-by: Glauber Costa \u003cglommer@redhat.com\u003e\nCC: Jan Kiszka \u003cjan.kiszka@web.de\u003e\nSigned-off-by: Marcelo Tosatti \u003cmtosatti@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "af701a441229a0cfec0ad36506ec1240844597f4",
      "old_mode": 33188,
      "old_path": "target-i386/cpu.h",
      "new_id": "5f1df8b4d3c10003b8e2e6163eeda40fc684f4a3",
      "new_mode": 33188,
      "new_path": "target-i386/cpu.h"
    },
    {
      "type": "modify",
      "old_id": "8a8724416761b26b49c1704bc3fea777736f0d40",
      "old_mode": 33188,
      "old_path": "target-i386/kvm.c",
      "new_id": "ba183c41594978170c92131c73a9e6086f7a8044",
      "new_mode": 33188,
      "new_path": "target-i386/kvm.c"
    }
  ]
}