)]}'
{
  "commit": "9102dedaa1ee1e89ce4a81283c403ff4928e9ef9",
  "tree": "d98546ef77e276c3afea8397fd76c1e0d46d1922",
  "parents": [
    "aed807c8e2bf009b2c6a35490d4fd4383887221d"
  ],
  "author": {
    "name": "Paolo Bonzini",
    "email": "pbonzini@redhat.com",
    "time": "Tue Aug 18 06:52:09 2015 -0700"
  },
  "committer": {
    "name": "Paolo Bonzini",
    "email": "pbonzini@redhat.com",
    "time": "Wed Sep 09 15:34:54 2015 +0200"
  },
  "message": "use qemu_cpu_kick instead of cpu_exit or qemu_cpu_kick_thread\n\nUse the same API to trigger interruption of a CPU, no matter if\nunder TCG or KVM.  There is no difference: these calls come from\nthe CPU thread, so the qemu_cpu_kick calls will send a signal\nto the running thread and it will be processed synchronously,\njust like a call to cpu_exit.  The only difference is in the\noverhead, but neither call to cpu_exit (now qemu_cpu_kick)\nis in a hot path.\n\nReviewed-by: Richard Henderson \u003crth@twiddle.net\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "dd2fc29afa838d5192d7b7e7373aff3ae1447816",
      "old_mode": 33188,
      "old_path": "cpus.c",
      "new_id": "e4079103ce587ed9cf2ea191585279887d0f4d30",
      "new_mode": 33188,
      "new_path": "cpus.c"
    },
    {
      "type": "modify",
      "old_id": "ffe7e6efb280e9472a9974e1556bcdf296090523",
      "old_mode": 33188,
      "old_path": "gdbstub.c",
      "new_id": "a5a173ab459b0705444c13d2becb4504b7155e7a",
      "new_mode": 33188,
      "new_path": "gdbstub.c"
    },
    {
      "type": "modify",
      "old_id": "2986f94f03256a36078bd62dbb4073ec84dac935",
      "old_mode": 33188,
      "old_path": "hw/ppc/spapr_rtas.c",
      "new_id": "9869bc95874c325377759ea61ec2c9b0a3fea30f",
      "new_mode": 33188,
      "new_path": "hw/ppc/spapr_rtas.c"
    }
  ]
}