)]}'
{
  "commit": "ac0fbbb2d02bc68b3c0bbc873e40dc0d75e71f4d",
  "tree": "17dff6674bc7730c79f0bb958ad42021e9c0ddbd",
  "parents": [
    "c0b2f0dd6ba71cc4e31d92eb0f8571a4b37d3853"
  ],
  "author": {
    "name": "Aditya Gupta",
    "email": "adityag@linux.ibm.com",
    "time": "Wed Jul 31 11:20:20 2024 +0530"
  },
  "committer": {
    "name": "Nicholas Piggin",
    "email": "npiggin@gmail.com",
    "time": "Mon Nov 04 09:11:45 2024 +1000"
  },
  "message": "target/ppc: Fix regression due to Power10 and Power11 having same PCR\n\nPower11 has the same PCR (Processor Compatibility Register) value, as\nPower10.\n\nDue to this, QEMU considers Power11 as a valid compat-mode for Power10,\nie. earlier it was possible to run QEMU with\n\u0027-M pseries,max-compat-mode\u003dpower11 --cpu power10\u0027\n\nSame PCR also introduced a regression where `-M pseries --cpu power10`\nboots as Power11 (ie. logical PVR is of Power11, even though PVR is\nPower10).  The regression was due to \u0027do_client_architecture_support\u0027\nchecking for valid compat modes and finding Power11 to be a valid compat\nmode for Power10 (it happens even without passing \u0027max-compat-mode\u0027\nexplicitly).\n\nFix compat-mode issue and regression, by ensuring a future Power\nprocessor (with a higher logical_pvr value, eg. P11) cannot be valid\ncompat-mode for an older Power processor (eg. P10)\n\nReviewed-by: Nicholas Piggin \u003cnpiggin@gmail.com\u003e\nSigned-off-by: Aditya Gupta \u003cadityag@linux.ibm.com\u003e\nTested-by: Amit Machhiwal \u003camachhiw@linux.ibm.com\u003e\nSigned-off-by: Nicholas Piggin \u003cnpiggin@gmail.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ebef2cccecf300b0b6f1663d648da68ed805a905",
      "old_mode": 33188,
      "old_path": "target/ppc/compat.c",
      "new_id": "5b20fd7ef04cab55776418a0bd78bbd5bd79de58",
      "new_mode": 33188,
      "new_path": "target/ppc/compat.c"
    }
  ]
}