)]}'
{
  "commit": "08b2d15cdd0d3fbbe37ce23bf192b770db3a7539",
  "tree": "1de106fb1e6aad474bc9b6db5dbed5a250784c8a",
  "parents": [
    "ab0c7fb22b56523f24d6e127cd4d10ecff67bf85"
  ],
  "author": {
    "name": "Paolo Bonzini",
    "email": "pbonzini@redhat.com",
    "time": "Mon Mar 18 17:45:56 2024 -0400"
  },
  "committer": {
    "name": "Paolo Bonzini",
    "email": "pbonzini@redhat.com",
    "time": "Tue Apr 23 17:35:25 2024 +0200"
  },
  "message": "runstate: skip initial CPU reset if reset is not actually possible\n\nRight now, the system reset is concluded by a call to\ncpu_synchronize_all_post_reset() in order to sync any changes\nthat the machine reset callback applied to the CPU state.\n\nHowever, for VMs with encrypted state such as SEV-ES guests (currently\nthe only case of guests with non-resettable CPUs) this cannot be done,\nbecause guest state has already been finalized by machine-init-done notifiers.\ncpu_synchronize_all_post_reset() does nothing on these guests, and actually\nwe would like to make it fail if called once guest has been encrypted.\nSo, assume that boards that support non-resettable CPUs do not touch\nCPU state and that all such setup is done before, at the time of\ncpu_synchronize_all_post_init().\n\nReviewed-by: Philippe Mathieu-Daudé \u003cphilmd@linaro.org\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d6ab860ecaa7f1f24df968f723c1ad5ab936f1ae",
      "old_mode": 33188,
      "old_path": "system/runstate.c",
      "new_id": "cb4905a40fce05bb657955bf3d4adbba6d09570f",
      "new_mode": 33188,
      "new_path": "system/runstate.c"
    }
  ]
}