ANDROID: 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.

Bug: 357781595
Change-Id: Id1642243ca4105a23e808cf28d13bfb81d9a5ac2
Signed-off-by: Keir Fraser <keirf@google.com>
This commit is contained in:
Keir Fraser
2023-01-24 11:11:09 +00:00
parent 0004939009
commit 789632c38b
2 changed files with 3 additions and 3 deletions
+2 -2
View File
@@ -17,7 +17,7 @@ Specific Hypervisor Service Call" range with a UID of
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 @@ Provides a discovery mechanism for other KVM/arm64 hypercalls.
| | (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
+1 -1
View File
@@ -7,7 +7,7 @@ PTP_KVM is used for high precision time sync between host and guests.
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