)]}'
{
  "commit": "dcaadc26fda20e920e05828f488fe5b10f00a3de",
  "tree": "e368d95a38f336471c2ca2e789bc029c541bec52",
  "parents": [
    "38b6e003879a872fc2bcc2c33a7016c8e67ccc93"
  ],
  "author": {
    "name": "Bibo Mao",
    "email": "maobibo@loongson.cn",
    "time": "Thu Oct 29 16:56:54 2026 +0800"
  },
  "committer": {
    "name": "Bibo Mao",
    "email": "maobibo@loongson.cn",
    "time": "Thu Nov 05 14:50:32 2026 +0800"
  },
  "message": "target/loongarch: Check CPU msgint feature with cpu_has_msgint()\n\nThere are two ways to check the CPU msgint feature. One is to call\ncpu_has_msgint(); the other is to check CPULoongArchState::msgint, which\nhas type OnOffAuto. A problem arises if msgint is set to ON_OFF_AUTO_AUTO\nin KVM mode: QEMU checks the host feature and sets its actual value in\ncpucfg1, which is read by cpu_has_msgint(). However, the msgint field\nremains ON_OFF_AUTO_AUTO.\n\nTherefore, in KVM mode cpu_has_msgint() is more accurate than checking\nthe OnOffAuto-typed msgint field.\n\nA problem occurs when booting a VM with the max CPU type on an LA464 host\nthat does not support msgint. cpu_has_msgint() returns false, but the\nmsgint field remains ON_OFF_AUTO_AUTO, so the expression\ncpu-\u003emsgint !\u003d ON_OFF_AUTO_OFF evaluates to true.\n\nSigned-off-by: Bibo Mao \u003cmaobibo@loongson.cn\u003e\nReviewed-by: Xianglai Li \u003clixianglai@loongson.cn\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "33bd89be8967e67ac436adaa718393c82e3dc4d5",
      "old_mode": 33188,
      "old_path": "hw/loongarch/virt.c",
      "new_id": "c67dad095ab5b47f11ff954569c269d0a212bef2",
      "new_mode": 33188,
      "new_path": "hw/loongarch/virt.c"
    },
    {
      "type": "modify",
      "old_id": "dd70beca1859eb6ec61bc64c12c78aaf6785b1cb",
      "old_mode": 33188,
      "old_path": "target/loongarch/cpu.c",
      "new_id": "1f3022265a71c579b95ae4456a71e54a243f3d51",
      "new_mode": 33188,
      "new_path": "target/loongarch/cpu.c"
    }
  ]
}
