KVM: arm64: Consistent hypercall naming in documentation Change a few uses of ARM_SMCCC_VENDOR_HYP_KVM_FOO_FUNC_ID to ARM_SMCCC_KVM_FUNC_FOO. Signed-off-by: Keir Fraser <keirf@google.com>
diff --git a/Documentation/virt/kvm/arm/hypercalls.rst b/Documentation/virt/kvm/arm/hypercalls.rst index d96c9fd..5ef81df 100644 --- a/Documentation/virt/kvm/arm/hypercalls.rst +++ b/Documentation/virt/kvm/arm/hypercalls.rst
@@ -17,7 +17,7 @@ guest using the standard "Call UID" function for the service range in order to determine that the KVM/arm64-specific hypercalls are available. -``ARM_SMCCC_VENDOR_HYP_KVM_FEATURES_FUNC_ID`` +``ARM_SMCCC_KVM_FUNC_FEATURES`` --------------------------------------------- Provides a discovery mechanism for other KVM/arm64 hypercalls. @@ -40,7 +40,7 @@ | | (uint32) | R3 | Bitmap of available function numbers 96-127 | +---------------------+----------+----+---------------------------------------------+ -``ARM_SMCCC_VENDOR_HYP_KVM_PTP_FUNC_ID`` +``ARM_SMCCC_KVM_FUNC_PTP`` ---------------------------------------- See ptp_kvm.rst
diff --git a/Documentation/virt/kvm/arm/ptp_kvm.rst b/Documentation/virt/kvm/arm/ptp_kvm.rst index 7c09609..c8b01b7 100644 --- a/Documentation/virt/kvm/arm/ptp_kvm.rst +++ b/Documentation/virt/kvm/arm/ptp_kvm.rst
@@ -7,7 +7,7 @@ It relies on transferring the wall clock and counter value from the host to the guest using a KVM-specific hypercall. -``ARM_SMCCC_VENDOR_HYP_KVM_PTP_FUNC_ID`` +``ARM_SMCCC_KVM_FUNC_PTP`` ---------------------------------------- Retrieve current time information for the specific counter. There are no