)]}'
{
  "commit": "6fa79e6cb0b409ff9bca429bf1da07df37d821dd",
  "tree": "eeeeadab7abe0191774c897dee840acc00941dd0",
  "parents": [
    "6ffcfca2b8ced270f971215092b9a8eae4285d8e"
  ],
  "author": {
    "name": "Fuad Tabba",
    "email": "fuad.tabba@linux.dev",
    "time": "Mon Aug 31 18:24:56 2026 +0100"
  },
  "committer": {
    "name": "Fuad Tabba",
    "email": "fuad.tabba@linux.dev",
    "time": "Mon Aug 31 20:11:24 2026 +0100"
  },
  "message": "arm64: Query counter-offset support on the VM fd\n\nkvm__arch_set_counter_offset() probes KVM_CAP_COUNTER_OFFSET with\nkvm__supports_extension(), which issues KVM_CHECK_EXTENSION on the\nglobal /dev/kvm fd. That reports the host\u0027s raw capabilities, unaware of\nany per-VM restrictions.\n\npKVM does not offer the counter offset to a protected VM, and reflects\nthat on the VM fd alone. kvmtool\u0027s own check passes, and the\nKVM_ARM_SET_COUNTER_OFFSET that follows is refused by\ncommit b12b3b04f6ba (\"KVM: arm64: Check whether a VM IOCTL is allowed\nin pKVM\"):\n\n  KVM_ARM_SET_COUNTER_OFFSET: Invalid argument\n\nQuery it on the VM fd via kvm__supports_vm_extension(), so\n--counter-offset on a protected VM fails with kvmtool\u0027s own message:\n\n  Fatal: No support for global counter offset\n\nSigned-off-by: Fuad Tabba \u003cfuad.tabba@linux.dev\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "36b3284e4a929fe101dd531a1e4da84b86728c7b",
      "old_mode": 33188,
      "old_path": "arm64/kvm.c",
      "new_id": "0bb35359e6f099e2e7419aafec93d01fab94324a",
      "new_mode": 33188,
      "new_path": "arm64/kvm.c"
    }
  ]
}
