)]}'
{
  "commit": "83e340b1d4205159b59f92763647824fe2048a50",
  "tree": "a4acc4066bf7414be722f9a35be555c71b7ecf96",
  "parents": [
    "728b17ecf4f968a3ba81da83c89b7e0342f47700"
  ],
  "author": {
    "name": "Will Deacon",
    "email": "willdeacon@google.com",
    "time": "Mon Jul 03 14:39:53 2023 +0100"
  },
  "committer": {
    "name": "Fuad Tabba",
    "email": "tabba@google.com",
    "time": "Thu Apr 17 13:16:03 2025 +0100"
  },
  "message": "KVM: arm64: Introduce new spinlock for hypervisor VM vCPUs[] array\n\nThe vCPU structures of the hypervisor VM struct claim to be protected\nby \u0027vm_table_lock\u0027, however:\n\n  1. This doesn\u0027t appear to be the case on the PSCI paths, where the\n     array is walked locklessly when accessing the target vCPU\n\n  2. The \u0027vm_table_lock\u0027 serialises across all VMs, so is overkill\n\nIntroduce a new per-VM spinlock for the vCPU array and ensure that it is\nheld whilst accessing the data structure.\n\nChange-Id: I316f6710af5f3147195d4b13e39b7cf5964e8589\nSigned-off-by: Will Deacon \u003cwill@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "362302abffdb2c0111818c0719ef61daa284aee7",
      "old_mode": 33188,
      "old_path": "arch/arm64/kvm/hyp/include/nvhe/pkvm.h",
      "new_id": "18f52176f9ae5bdbc197977bf028e03a837b0b58",
      "new_mode": 33188,
      "new_path": "arch/arm64/kvm/hyp/include/nvhe/pkvm.h"
    },
    {
      "type": "modify",
      "old_id": "c92cb9743c9acd24145ea17d3cb8a5e65fdbe33d",
      "old_mode": 33188,
      "old_path": "arch/arm64/kvm/hyp/nvhe/pkvm.c",
      "new_id": "d99ba6491a5d77666c8cd11023c8a07ce669700a",
      "new_mode": 33188,
      "new_path": "arch/arm64/kvm/hyp/nvhe/pkvm.c"
    }
  ]
}