)]}'
{
  "commit": "1fb5a622f7ef0cfd65b39decd768983e1d0ba1c2",
  "tree": "829d55f65654e75256d939b050f5f9f5bf37cfe5",
  "parents": [
    "d758f8849851dd4e97a575e52c11ec748ab1bbec"
  ],
  "author": {
    "name": "Daniel Henrique Barboza",
    "email": "dbarboza@ventanamicro.com",
    "time": "Thu Jul 06 07:17:26 2023 -0300"
  },
  "committer": {
    "name": "Alistair Francis",
    "email": "alistair.francis@wdc.com",
    "time": "Mon Jul 10 22:29:15 2023 +1000"
  },
  "message": "target/riscv: handle mvendorid/marchid/mimpid for KVM CPUs\n\nAfter changing user validation for mvendorid/marchid/mimpid to guarantee\nthat the value is validated on user input time, coupled with the work in\nfetching KVM default values for them by using a scratch CPU, we\u0027re\ncertain that the values in cpu-\u003ecfg.(mvendorid|marchid|mimpid) are\nalready good to be written back to KVM.\n\nThere\u0027s no need to write the values back for \u0027host\u0027 type CPUs since the\nvalues can\u0027t be changed, so let\u0027s do that just for generic CPUs.\n\nSigned-off-by: Daniel Henrique Barboza \u003cdbarboza@ventanamicro.com\u003e\nReviewed-by: Andrew Jones \u003cajones@ventanamicro.com\u003e\nAcked-by: Alistair Francis \u003calistair.francis@wdc.com\u003e\nMessage-Id: \u003c20230706101738.460804-9-dbarboza@ventanamicro.com\u003e\nSigned-off-by: Alistair Francis \u003calistair.francis@wdc.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d8c1423b549201abe45958d3866eadf5f9234458",
      "old_mode": 33188,
      "old_path": "target/riscv/kvm.c",
      "new_id": "f264286d5121b82ac1c5e8a71d072a2d350d9091",
      "new_mode": 33188,
      "new_path": "target/riscv/kvm.c"
    }
  ]
}