)]}'
{
  "commit": "b4a3d965dee06d52281496bb5fd0a5cb5534b545",
  "tree": "3d1c0bb7600ea91eea18e27530c3afa2ec41bbf7",
  "parents": [
    "aa2c364b4cf2fae4d9c8acf53ee4436ed533902d"
  ],
  "author": {
    "name": "Jan Kiszka",
    "email": "jan.kiszka@siemens.com",
    "time": "Tue Feb 01 22:15:43 2011 +0100"
  },
  "committer": {
    "name": "Marcelo Tosatti",
    "email": "mtosatti@redhat.com",
    "time": "Mon Feb 14 12:39:44 2011 -0200"
  },
  "message": "Stop current VCPU on synchronous reset requests\n\nIf some I/O operation ends up calling qemu_system_reset_request in VCPU\ncontext, we record this and inform the io-thread, but we do not\nterminate the VCPU loop. This can lead to fairly unexpected behavior if\nthe triggering reset operation is supposed to work synchronously.\n\nFix this for TCG (when run in deterministic I/O mode) by setting the\nVCPU on stop and issuing a cpu_exit. KVM requires some more work on its\nVCPU loop.\n\n[ ported from qemu-kvm ]\n\nSigned-off-by: Jan Kiszka \u003cjan.kiszka@siemens.com\u003e\nSigned-off-by: Marcelo Tosatti \u003cmtosatti@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ab6e40e93d5c886db295601546ac532462e6a45d",
      "old_mode": 33188,
      "old_path": "cpus.c",
      "new_id": "f8a88e3bb4b237120112dd5e16c88c7832b0cf12",
      "new_mode": 33188,
      "new_path": "cpus.c"
    },
    {
      "type": "modify",
      "old_id": "bf4d9bb87a75f521aed366a50d6257708aeab702",
      "old_mode": 33188,
      "old_path": "cpus.h",
      "new_id": "4cadb641c0c27f3dc2b6c6374485788b90e29810",
      "new_mode": 33188,
      "new_path": "cpus.h"
    },
    {
      "type": "modify",
      "old_id": "ed2cdfae421815d5fd238113a8d9143e1bd409f9",
      "old_mode": 33188,
      "old_path": "vl.c",
      "new_id": "5e3f7f24e9b8aa0771d117fb59610c3c15691803",
      "new_mode": 33188,
      "new_path": "vl.c"
    }
  ]
}