)]}'
{
  "commit": "864867b91b48d38e2bfc7b225197901e6f7d8216",
  "tree": "0a50bc8d7cc9863b214849b72466682a96d6ae55",
  "parents": [
    "1cadaa9482244f7d6477afc34c04a5dad84afdde"
  ],
  "author": {
    "name": "Eduardo Habkost",
    "email": "ehabkost@redhat.com",
    "time": "Fri Oct 03 16:39:48 2014 -0300"
  },
  "committer": {
    "name": "Andreas Färber",
    "email": "afaerber@suse.de",
    "time": "Tue Nov 04 15:35:47 2014 +0100"
  },
  "message": "target-i386: Disable CPUID_ACPI by default in KVM mode\n\nKVM never supported the CPUID_ACPI flag, so it doesn\u0027t make sense to\nhave it enabled by default when KVM is enabled.\n\nThe motivation here is exactly the same we had for the MONITOR flag\n(disabled by commit 136a7e9a85d7047461f8153f7d12c514a3d68f69).\n\nAnd like in the MONITOR flag case, we don\u0027t need machine-type compat code\nbecause it is currently impossible to run a KVM VM with the ACPI flag set.\n\nSigned-off-by: Eduardo Habkost \u003cehabkost@redhat.com\u003e\nSigned-off-by: Andreas Färber \u003cafaerber@suse.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1b25965a64a51f1b26ebd800a2d7cf88d3dd54d6",
      "old_mode": 33188,
      "old_path": "target-i386/cpu.c",
      "new_id": "727416ead9b7bb0fc62d490aea8980e5bcd74c60",
      "new_mode": 33188,
      "new_path": "target-i386/cpu.c"
    }
  ]
}