)]}'
{
  "commit": "ae46e23964ad45d5bc72374040e87d8f52ac2178",
  "tree": "f33f22a3d54807a496cdc552736cb31f59c50b40",
  "parents": [
    "fb1a3a051d89975f26296163066bb0745ecca49d"
  ],
  "author": {
    "name": "Paul Donohue",
    "email": "qemu-devel@PaulSD.com",
    "time": "Fri Jun 12 10:10:14 2015 -0400"
  },
  "committer": {
    "name": "Paolo Bonzini",
    "email": "pbonzini@redhat.com",
    "time": "Fri Jun 19 12:27:14 2015 +0200"
  },
  "message": "mc146818rtc: Reset the periodic timer on load\n\nWhen loading a VM from a snapshot or migration, clock changes can cause\nthe periodic timer to stall or loop rapidly.\n\nqemu-timer has a reset notifier mechanism that is used to avoid timer\nstalls or loops if the host clock changes while the VM is running when\nusing QEMU_CLOCK_HOST.  However, when loading a snapshot or migration,\nqemu-timer is initialized and fires the reset notifier before\nmc146818rtc is initialized and has registered its reset handler.  In\naddition, this mechanism isn\u0027t used when using QEMU_CLOCK_REALTIME,\nwhich might also change when loading a snapshot or migration.\n\nTo correct that problem, this commit resets the periodic timer after\nloading from a snapshot or migration if the clock has either jumped\nbackward or has jumped forward by more than the clock jump limit that\nis used by the reset notifier code in qemu-timer.\n\nSigned-off-by: Paul Donohue \u003cqemu-git@PaulSD.com\u003e\nMessage-Id: \u003c20150612141013.GE2749@TopQuark.net\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "32048258c963147717831b1adb233a2ab233fccd",
      "old_mode": 33188,
      "old_path": "hw/timer/mc146818rtc.c",
      "new_id": "2e3ffc8c073e7f722d9149ea601fb5da0c7e363a",
      "new_mode": 33188,
      "new_path": "hw/timer/mc146818rtc.c"
    }
  ]
}