@@ -23,21 +23,23 @@ the PV_TIME_FEATURES hypercall should be probed using the SMCCC 1.1
2323ARCH_FEATURES mechanism before calling it.
2424
2525PV_TIME_FEATURES
26- ============= ======== ==========
26+
27+ ============= ======== =================================================
2728 Function ID: (uint32) 0xC5000020
2829 PV_call_id: (uint32) The function to query for support.
2930 Currently only PV_TIME_ST is supported.
3031 Return value: (int64) NOT_SUPPORTED (-1) or SUCCESS (0) if the relevant
3132 PV-time feature is supported by the hypervisor.
32- ============= ======== ==========
33+ ============= ======== =================================================
3334
3435PV_TIME_ST
35- ============= ======== ==========
36+
37+ ============= ======== ==============================================
3638 Function ID: (uint32) 0xC5000021
3739 Return value: (int64) IPA of the stolen time data structure for this
3840 VCPU. On failure:
3941 NOT_SUPPORTED (-1)
40- ============= ======== ==========
42+ ============= ======== ==============================================
4143
4244The IPA returned by PV_TIME_ST should be mapped by the guest as normal memory
4345with inner and outer write back caching attributes, in the inner shareable
@@ -76,5 +78,5 @@ It is advisable that one or more 64k pages are set aside for the purpose of
7678these structures and not used for other purposes, this enables the guest to map
7779the region using 64k pages and avoids conflicting attributes with other memory.
7880
79- For the user space interface see Documentation/virt/kvm/devices/vcpu.rst
80- section "3. GROUP: KVM_ARM_VCPU_PVTIME_CTRL" .
81+ For the user space interface see
82+ :ref: ` Documentation/virt/kvm/devices/vcpu.rst < kvm_arm_vcpu_pvtime_ctrl >` .
0 commit comments