diff options
| author | Suzuki K Poulose <suzuki.poulose@arm.com> | 2026-10-07 08:35:28 +0100 |
|---|---|---|
| committer | Marc Zyngier <maz@kernel.org> | 2026-10-07 13:30:28 +0100 |
| commit | 762ad274c03a13686192d75ef9a354b96114b503 (patch) | |
| tree | c3c3fbfa8012419a143705f3b7a12935571c9e2e /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 0c4063f89bfdf204112651f45620ef0c5a691e6b (diff) | |
KVM: arm64: Track the type of VM in kvm_arch
KVM arm64 has different types of VMs with all the different modes in which
the hypervisor code can be run. e.g., VHE, nVHE, pKVM etc. Then there is
protected VM and normal VMs with pKVM. We might soon add other types,
e.g., Arm CCA Realm. So in an effort to make the handling of these
different types of VMs a bit more friendly to the eyes, add a VM flavor to
the kvm_arch and we could then add handlers for different operations based
on the VM type.
Keep the flavor initialisation at the beginning to allow for the detection
early enough and fail out on any unsupported requests.
With that, add wrappers for checking the "type" of a VM and replace the
existing users with the new wrappers.
Given we already have the construct of "kvm_vm_is_protected" in the core
KVM code, use that for all confidential compute guests including Realms
that we are about to add. Adds __VM_PROTECTED marker vm flavor to draw the
boundary for "protected VMs". In later patches, we would add Realm VMs,
which would also be classified as protected.
While adding the vm_flavor, move the psci_version around to keep the structure
packed.
Suggested-by: Marc Zyngier <maz@kernel.org>
Reviewed-by: Gavin Shan <gshan@redhat.com>
Tested-by: Gavin Shan <gshan@redhat.com>
Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Link: https://patch.msgid.link/20261007073537.2454351-6-suzuki.poulose@arm.com
Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions
