Roman Kisel 13423063c7 arm64: kvm, smccc: Introduce and use API for getting hypervisor UUID ... The KVM/arm64 uses SMCCC to detect hypervisor presence. That code is private, and it follows the SMCCC specification. Other existing and emerging hypervisor guest implementations can and should use that standard approach as well. Factor out a common infrastructure that the guests can use, update KVM to employ the new API. The central notion of the SMCCC method is the UUID of the hypervisor, and the new API follows that. No functional changes. Validated with a KVM/arm64 guest. Signed-off-by: Roman Kisel <romank@linux.microsoft.com> Acked-by: Arnd Bergmann <arnd@arndb.de> Reviewed-by: Michael Kelley <mhklinux@outlook.com> Link: https://lore.kernel.org/r/20250428210742.435282-2-romank@linux.microsoft.com Signed-off-by: Wei Liu <wei.liu@kernel.org> Message-ID: <20250428210742.435282-2-romank@linux.microsoft.com>		2025-05-23 16:30:55 +00:00
..
Kconfig	firmware: smccc: Add ARCH_SOC_ID support	2020-07-06 09:48:06 +01:00
kvm_guest.c	arm64: kvm, smccc: Introduce and use API for getting hypervisor UUID	2025-05-23 16:30:55 +00:00
Makefile	arm/arm64: Probe for the presence of KVM hypervisor	2021-03-31 09:16:55 +01:00
smccc.c	arm64: kvm, smccc: Introduce and use API for getting hypervisor UUID	2025-05-23 16:30:55 +00:00
soc_id.c	firmware: smccc: Support optional Arm SMCCC SOC_ID name	2025-03-03 14:53:46 +00:00