)]}'
{
  "commit": "9705fbb5636fbe36956e6886227e9e871689cf83",
  "tree": "1ed88bd7ff2299e8d855207d8347069ec99e1153",
  "parents": [
    "67bb172f9d995880a9c752e9f33819f4a63a3fda"
  ],
  "author": {
    "name": "Paolo Bonzini",
    "email": "pbonzini@redhat.com",
    "time": "Sat Mar 12 17:44:00 2011 +0100"
  },
  "committer": {
    "name": "Blue Swirl",
    "email": "blauwirbel@gmail.com",
    "time": "Sun Mar 13 14:44:22 2011 +0000"
  },
  "message": "do not use timedwait on qemu_halt_cond\n\nThe following conditions can cause cpu_has_work(env) to become true:\n\n- env-\u003equeued_work_first: run_on_cpu is already kicking the VCPU\n\n- env-\u003estop \u003d 1: pause_all_vcpus is already kicking the VCPU\n\n- env-\u003estopped \u003d 0: resume_all_vcpus is already kicking the VCPU\n\n- vm_running \u003d 1: vm_start is calling resume_all_vcpus\n\n- env-\u003ehalted \u003d 0: see previous patch\n\n- qemu_cpu_has_work(env): when it becomes true, board code should set\n  env-\u003ehalted \u003d 0 too.\n\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\nSigned-off-by: Blue Swirl \u003cblauwirbel@gmail.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6cfb45b01dddc73fcb6a16e43a2116925bcaed84",
      "old_mode": 33188,
      "old_path": "cpus.c",
      "new_id": "4c3837f120b9a05daa195cdb99aa696097eea1b8",
      "new_mode": 33188,
      "new_path": "cpus.c"
    }
  ]
}