From: Roman Kisel <rom...@linux.microsoft.com> Sent: Monday, April 14, 2025 3:47 PM > > 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 <rom...@linux.microsoft.com> > --- > arch/arm64/kvm/hypercalls.c | 10 +++-- > drivers/firmware/smccc/kvm_guest.c | 10 +---- > drivers/firmware/smccc/smccc.c | 17 ++++++++ > include/linux/arm-smccc.h | 64 ++++++++++++++++++++++++++++-- > 4 files changed, 85 insertions(+), 16 deletions(-) >
Reviewed-by: Michael Kelley <mhkli...@outlook.com>
